] Document `return` parameters without `scope`
Part of Issue 17934 - [scope] scopeness entrypoint for unique/ref-counted
missing.
Add 'Struct Return Methods' subheading.
https://github.com/dlang/dlang.org/pull/3619
--
created dlang/dlang.org pull request #3619 "[spec/function] Document
`return` parameters without `scope`" fixing this issue:
- [spec/function] Document `return` parameters without `scope`
Fixes Issue 17934 - [scope] scopeness entrypoint for unique/ref-counted
missing.
https://
https://issues.dlang.org/show_bug.cgi?id=17934
--- Comment #12 from Nick Treleaven ---
If you define `front` as `return`, *not* `return scope`:
Elem front() @safe return
You get an error for:
elem = l.front;
I think that fixes this issue, though that feature may need documenting.
--
https://issues.dlang.org/show_bug.cgi?id=17934
Paul Backus changed:
What|Removed |Added
CC||snarwin+bugzi...@gmail.com
--- Comment #11
https://issues.dlang.org/show_bug.cgi?id=17934
Iain Buclaw changed:
What|Removed |Added
Priority|P3 |P4
--
quot;fix Issue 17934 - [scope] scopeness entrypoint for unique/ref-counted
missing"
This reverts commit 18ad1685dcdca65070f7a1d89efa4410a5936895.
https://github.com/dlang/dmd/pull/13926
--
https://issues.dlang.org/show_bug.cgi?id=17934
Nick Treleaven changed:
What|Removed |Added
CC||n...@geany.org
--- Comment #9 from Nick
https://issues.dlang.org/show_bug.cgi?id=17934
--- Comment #8 from Dlang Bot ---
@dkorpel created dlang/dmd pull request #13926 "Revert "fix Issue 17934 -
[scope] scopeness entrypoint for unique/ref…" mentioning this issue:
- Revert "fix Issue 17934 - [scope] scopeness entry
https://issues.dlang.org/show_bug.cgi?id=17934
Mike Franklin changed:
What|Removed |Added
CC||slavo5...@yahoo.com
--- Comment #7 from
https://issues.dlang.org/show_bug.cgi?id=17934
Walter Bright changed:
What|Removed |Added
Severity|normal |enhancement
--- Comment #6 from Walter
https://issues.dlang.org/show_bug.cgi?id=17934
Walter Bright changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://issues.dlang.org/show_bug.cgi?id=17934
--- Comment #5 from github-bugzi...@puremagic.com ---
Commit pushed to stable at https://github.com/dlang/dmd
https://github.com/dlang/dmd/commit/18ad1685dcdca65070f7a1d89efa4410a5936895
fix Issue 17934 - [scope] scopeness entrypoint for unique/ref
https://issues.dlang.org/show_bug.cgi?id=17934
github-bugzi...@puremagic.com changed:
What|Removed |Added
Status|NEW |RESOLVED
https://issues.dlang.org/show_bug.cgi?id=17934
--- Comment #4 from github-bugzi...@puremagic.com ---
Commit pushed to master at https://github.com/dlang/dmd
https://github.com/dlang/dmd/commit/18ad1685dcdca65070f7a1d89efa4410a5936895
fix Issue 17934 - [scope] scopeness entrypoint for unique/ref
https://issues.dlang.org/show_bug.cgi?id=17934
--- Comment #3 from Walter Bright ---
https://github.com/dlang/dmd/pull/7284
--
https://issues.dlang.org/show_bug.cgi?id=17934
--- Comment #2 from Walter Bright ---
It sounds like the solution is to infer 'scope' for a struct instance on the
stack if it has a destructor.
--
https://issues.dlang.org/show_bug.cgi?id=17934
--- Comment #1 from Martin Nowak ---
Even if `l` is not inferred as scope, it should be a local with limited
lifetime.
The return value `l.front` should have that same lifetime b/c of `return
scope`.
Both of them should be shorter as
17 matches
Mail list logo