You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the trace functions are emitted in a separate pass primarilly because they are magic and EmitC adds a bit of extra text at the top of the trace functions. I would like to get rid of this and add any text necessary into the function bodies via AstText and friends so Emit does not need to know.
This would mean trace and implementation fucntions could be emitted by the same pass. The only question I have is whether we would like to keep the __Trace substring in the file names, or can we just put trace and implementation functions together ? Apart from reading the file names/build output, this makes no difference today at all. Fast/slow code would still be separate of course.
The text was updated successfully, but these errors were encountered:
Currently the trace functions are emitted in a separate pass primarilly because they are magic and EmitC adds a bit of extra text at the top of the trace functions. I would like to get rid of this and add any text necessary into the function bodies via AstText and friends so Emit does not need to know.
This would mean trace and implementation fucntions could be emitted by the same pass. The only question I have is whether we would like to keep the __Trace substring in the file names, or can we just put trace and implementation functions together ? Apart from reading the file names/build output, this makes no difference today at all. Fast/slow code would still be separate of course.
The text was updated successfully, but these errors were encountered: