While PR #928 (#928) successfully addresses Python documentation extraction, it causes the TestClang test case to fail. An examination of the newly generated Go code's doc comments reveals numerous discrepancies with the original documentation, as well as garbled content (such as **/). Please adjust the code responsible for C/C++ comment formatting to ensure that comment extraction for both Clang and Python is handled correctly. Additionally, since the generated Go code varies slightly across platforms, we currently verify the output Go files specifically on macOS (refer to the runtime.GOOS != "darwin" conditions in tool/gen_test.go). If the sandbox environment does not support macOS, you may consider modifying these conditions to allow for non-macOS platforms as well.
While PR #928 (#928) successfully addresses Python documentation extraction, it causes the
TestClangtest case to fail. An examination of the newly generated Go code's doc comments reveals numerous discrepancies with the original documentation, as well as garbled content (such as**/). Please adjust the code responsible for C/C++ comment formatting to ensure that comment extraction for both Clang and Python is handled correctly. Additionally, since the generated Go code varies slightly across platforms, we currently verify the output Go files specifically on macOS (refer to theruntime.GOOS != "darwin"conditions intool/gen_test.go). If the sandbox environment does not support macOS, you may consider modifying these conditions to allow for non-macOS platforms as well.