-
Notifications
You must be signed in to change notification settings - Fork 8
Open
Description
Issue: Handling Strict Syntax Errors in Go for Haxe->Go Compiler
Description:
I am experiencing an issue with my Haxe->Go compiler where Go is extremely strict about syntax errors in any .go file, regardless of whether the file is actually used by the main function or not. This results in compilation failures due to unused or irrelevant files.
Proposed Solutions:
-
Export to
Class.go.notif syntax check fails:- This would involve changing the default filename to indicate that the file has syntax errors, preventing it from being included in the compilation process.
-
Export to Directory Structure Instead of Flattening the Project:
- This approach would maintain the original directory structure of the project, rather than flattening it, in this case the go compiler will ignore folders that it doesn't have to look into, This would help prevent conflicts when two classes from different namespaces have the same name, as each class would reside in its respective directory.
Both of them will require me to programmatically change the name of the currently compiled class from Generator, how can I do that with reflaxe?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels