POC: automatically move scope array literals to the stack
See https://github.com/dlang/dmd/pull/16888#issuecomment-2379226685
Just a proof of concept, I don't think this is worth merging at this stage. Maybe under -preview=dip1000 only.
Thanks for your pull request and interest in making D better, @dkorpel! We are looking forward to reviewing it, and you should be hearing from a maintainer soon. Please verify that your PR follows this checklist:
- My PR is fully covered with tests (you can see the coverage diff by visiting the details link of the codecov check)
- My PR is as minimal as possible (smaller, focused PRs are easier to review than big ones)
- I have provided a detailed rationale explaining my changes
- New or modified functions have Ddoc comments (with
Params:andReturns:)
Please see CONTRIBUTING.md for more information.
If you have addressed all reviews or aren't sure how to proceed, don't hesitate to ping us with a simple comment.
Bugzilla references
Your PR doesn't reference any Bugzilla issue.
If your PR contains non-trivial changes, please reference a Bugzilla issue or create a manual changelog.
Testing this PR locally
If you don't have a local development environment setup, you can use Digger to test this PR:
dub run digger -- build "master + dmd#16897"
I assume you will make scope foo = [...] @nogc ?
I assume you will make
scope foo = [...]@nogc?
If this is actually worth pursuing, yes. It's non-trivial because currently, @nogc is eagerly checked on each expression, while in this case, an array literal expression can only be checked at the end of the function.
That patch could introduce dangling pointers in @safe code. -preview=dip1000 is required to verify the stack-allocated array literal doesn't escape.
-betterC simply disables language features that require druntime, it does not negate @safe or change language semantics in other ways, so checking for global.params.betterC likely isn't the right answer here.