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
Observation: Common feedback I see on C3 code is that there are many memory leaks. Goal: Promote the temporary allocator by making it a default choice in C3 0.7
Complimentary to that goal and observation may be detecting if there is a @pool(){} (or equivalent) in the context where the temporary allocator was used. This may then prompt people to the solution via an error or warning fix the memory leak issue, leading to a nice quality of life improvement.
The text was updated successfully, but these errors were encountered:
BTW, what if this @pool would initialize temp allocator engine internally too if it wasn't initialized before? Therefore, we might get rid of tmem() macro, in favor of tmem built-in (because all initialization mechanics will be in @pool call)
Observation: Common feedback I see on C3 code is that there are many memory leaks.
Goal: Promote the temporary allocator by making it a default choice in C3 0.7
Complimentary to that goal and observation may be detecting if there is a
@pool(){}
(or equivalent) in the context where the temporary allocator was used. This may then prompt people to the solution via an error or warning fix the memory leak issue, leading to a nice quality of life improvement.The text was updated successfully, but these errors were encountered: