Comment by amelius 15 hours ago How do compile errors propagate back from the target language to the source language? 4 comments amelius Reply usrnm 15 hours ago They are not supposed to produce code that doesn't compile, why would they? debugnik 14 hours ago Debugger positions on the other hand are a pain with these things. amelius 12 hours ago Uh yes, that's what I meant ;)In C/C++ you have the #line preprocessor directive. It would be nice if Go had something similar. 1 reply →
usrnm 15 hours ago They are not supposed to produce code that doesn't compile, why would they? debugnik 14 hours ago Debugger positions on the other hand are a pain with these things. amelius 12 hours ago Uh yes, that's what I meant ;)In C/C++ you have the #line preprocessor directive. It would be nice if Go had something similar. 1 reply →
debugnik 14 hours ago Debugger positions on the other hand are a pain with these things. amelius 12 hours ago Uh yes, that's what I meant ;)In C/C++ you have the #line preprocessor directive. It would be nice if Go had something similar. 1 reply →
amelius 12 hours ago Uh yes, that's what I meant ;)In C/C++ you have the #line preprocessor directive. It would be nice if Go had something similar. 1 reply →
They are not supposed to produce code that doesn't compile, why would they?
Debugger positions on the other hand are a pain with these things.
Uh yes, that's what I meant ;)
In C/C++ you have the #line preprocessor directive. It would be nice if Go had something similar.
1 reply →