On Sunday, 6 August 2017 at 02:19:19 UTC, FoxyBrown wrote:

I don't think you understand what I'm saying.

If I use this method to create a "reference" type on the stack rather than the heap, is the only issue worrying about not having that variable be used outside that scope(i.e., have it "escape")?

It's the only one I'm aware of OTTOMH. If you encounter others, a bug report would be appreciated.

Reply via email to