[Issue 24525] auto ref lambda exp not parsed if used as left-most expression in an expression statement

2024-05-01 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=24525 Dlang Bot changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Issue 24525] auto ref lambda exp not parsed if used as left-most expression in an expression statement

2024-05-01 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=24525 Dlang Bot changed: What|Removed |Added Keywords||pull --- Comment #4 from Dlang Bot --- @ntrel

[Issue 24525] auto ref lambda exp not parsed if used as left-most expression in an expression statement

2024-04-30 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=24525 Nick Treleaven changed: What|Removed |Added Assignee|nob...@puremagic.com|n...@geany.org --

[Issue 24525] auto ref lambda exp not parsed if used as left-most expression in an expression statement

2024-04-29 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=24525 basile-z changed: What|Removed |Added Summary|auto ref lambda exp not |auto ref lambda exp

[Issue 24525] auto ref lambda exp not parsed if used as left-most expression in a expression statement

2024-04-29 Thread d-bugmail--- via Digitalmars-d-bugs
e none. The parser should lookup after `auto`. If next is `(` or if next two are `ref` then `(`, then it should takes the path of expression. > It is unfortunate that the function literal syntax starting `ref` or `auto > ref` was added, when the function/delegate keyword starting forms can alrea

[Issue 24525] auto ref lambda exp not parsed if used as left-most expression in a expression statement

2024-04-28 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=24525 Nick Treleaven changed: What|Removed |Added Severity|enhancement |normal --- Comment #2 from Nick Treleaven

[Issue 24525] auto ref lambda exp not parsed if used as left-most expression in a expression statement

2024-04-28 Thread d-bugmail--- via Digitalmars-d-bugs
edence. For: > ref () {return a;}() = 0; A declaration `ref () {return a;}` gets parsed, not an ExpressionStatement. So I think this issue is invalid. It is unfortunate that the function literal syntax starting `ref` or `auto ref` was added, when the function/delegate keyword starting forms ca

[Issue 24525] New: auto ref lambda exp not parsed if used as left-most expression in a expression statement

2024-04-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=24525 Issue ID: 24525 Summary: auto ref lambda exp not parsed if used as left-most expression in a expression statement Product: D Version: D2 Hardware: All OS: All

[Issue 24513] `pure` can be used as `auto`

2024-04-19 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=24513 --- Comment #2 from basile-z --- that's completly stupid. Nobody would accept that in phobos. Just imagine my friend, someone who makes a PR that is like ``` pure takeWhile(T)(auto ref T t); ``` any human being would open a review comment to say

[Issue 24513] `pure` can be used as `auto`

2024-04-19 Thread d-bugmail--- via Digitalmars-d-bugs
||dkor...@live.nl Hardware|x86_64 |All Resolution|--- |INVALID OS|Linux |All --- Comment #1 from Dennis --- This is defined behavior: https://dlang.org/spec/function.html#auto-functions

[Issue 24513] New: `pure` can be used as `auto`

2024-04-19 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=24513 Issue ID: 24513 Summary: `pure` can be used as `auto` Product: D Version: D2 Hardware: x86_64 OS: Linux Status: NEW Keywords: accepts-invalid, diagnostic

[Issue 24385] New: Slicing a static array binds as non-ref when using auto ref

2024-02-10 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=24385 Issue ID: 24385 Summary: Slicing a static array binds as non-ref when using auto ref Product: D Version: D2 Hardware: All OS: All Status: NEW

Re: template/mixin magic for to! auto inferring type from variable

2024-02-03 Thread kdevel via Digitalmars-d-learn
On Saturday, 3 February 2024 at 02:20:13 UTC, Paul Backus wrote: On Friday, 2 February 2024 at 23:25:37 UTC, Chris Katko wrote: The auto solution won't work for a struct however which I'm using: ```D struct procTable{ //contains all the fields inside a file I'm parsing uint time; int

Re: template/mixin magic for to! auto inferring type from variable

2024-02-02 Thread Paul Backus via Digitalmars-d-learn
On Friday, 2 February 2024 at 23:25:37 UTC, Chris Katko wrote: The auto solution won't work for a struct however which I'm using: ```D struct procTable{ //contains all the fields inside a file I'm parsing uint time; int priority; string name; // etc } ``` Maybe you can use

Re: template/mixin magic for to! auto inferring type from variable

2024-02-02 Thread Chris Katko via Digitalmars-d-learn
On Friday, 2 February 2024 at 21:01:53 UTC, Paul Backus wrote: No, D only does bottom-up type inference, not top down. If you want to avoid repeating the type, use `auto` on the left side: ```d auto time = to!uint(data[1]); auto priority = to!int(data[2]); ``` Okay thanks. It finally

Re: template/mixin magic for to! auto inferring type from variable

2024-02-02 Thread Paul Backus via Digitalmars-d-learn
On Friday, 2 February 2024 at 07:43:09 UTC, Chris Katko wrote: Is there some way to do: ```D string[3] data; //strings from some file input, some are ints, uints, etc. auto into!(T)(T value){return to!???(value); } // ??? uint time = into!(data[1]); // We already know this is uint int

template/mixin magic for to! auto inferring type from variable

2024-02-01 Thread Chris Katko via Digitalmars-d-learn
Is there some way to do: ```D string[3] data; //strings from some file input, some are ints, uints, etc. auto into!(T)(T value){return to!???(value); } // ??? uint time = into!(data[1]); // We already know this is uint int priority = into!(data[2]); ``` instead of: ```D uint time = to!uint

Re: Would this be a useful construct to add to D? auto for constructor call.

2024-01-27 Thread Chris Katko via Digitalmars-d-announce
On Wednesday, 24 January 2024 at 08:22:49 UTC, Walter Bright wrote: On 1/23/2024 8:01 AM, Steven Schveighoffer wrote: zero proposals that infer type from how they are used have been accepted by Walter, this one probably will be no different. Types are inferred in D from the bottom up. Mixing

Re: Would this be a useful construct to add to D? auto for constructor call.

2024-01-24 Thread Walter Bright via Digitalmars-d-announce
On 1/23/2024 8:01 AM, Steven Schveighoffer wrote: zero proposals that infer type from how they are used have been accepted by Walter, this one probably will be no different. Types are inferred in D from the bottom up. Mixing in special cases of it being top down leads to confusion over how

Re: Would this be a useful construct to add to D? auto for constructor call.

2024-01-23 Thread Steven Schveighoffer via Digitalmars-d-announce
also can do some library tricks (unfortunately this won't count as construction, but probably is fine in most cases) ```d auto create(T, Args...)(out T val, Args args) { static if(is(T == class)) val = new T(args); else static if(...) // do eveyrything else. } ... dataGrid.create(15

Re: Would this be a useful construct to add to D? auto for constructor call.

2024-01-23 Thread Jonathan M Davis via Digitalmars-d-announce
On Tuesday, January 23, 2024 4:11:00 AM MST ryuukk_ via Digitalmars-d-announce wrote: > On Tuesday, 23 January 2024 at 06:30:08 UTC, Jonathan M Davis > > wrote: > > That being said, I expect that it would be pretty easy to write > > a mixin to do something like that if you really wanted to. > >

Re: Would this be a useful construct to add to D? auto for constructor call.

2024-01-23 Thread Sergey via Digitalmars-d-announce
On Tuesday, 23 January 2024 at 11:11:00 UTC, ryuukk_ wrote: [OT] btw what did you find? Which one could you recommend? https://forum.dlang.org/post/cqgrciflmvuwonsnz...@forum.dlang.org

Re: Would this be a useful construct to add to D? auto for constructor call.

2024-01-23 Thread ryuukk_ via Digitalmars-d-announce
On Tuesday, 23 January 2024 at 06:30:08 UTC, Jonathan M Davis wrote: That being said, I expect that it would be pretty easy to write a mixin to do something like that if you really wanted to. Also, if you're simply looking to not have to name the type, you could do dataGrid = new

Re: Would this be a useful construct to add to D? auto for constructor call.

2024-01-22 Thread Jonathan M Davis via Digitalmars-d-announce
) >{ >dataGrid = new auto(15); // <--- new >// instead of >dataGrid = new dataGridLayerView(15); >} > } > ``` > > Because it seems, conceptually, the compiler should know all the > details required here to simply insert

Would this be a useful construct to add to D? auto for constructor call.

2024-01-22 Thread Chris Katko via Digitalmars-d-announce
```D class dataGridLayerView{ int t; this(int _t){ t = _t; } } class myClass{ dataGridLayerView dataGrid; this() { dataGrid = new auto(15); // <--- new // instead of dataGrid = new dataGridLayerView(15); } } ``` Because it se

[Issue 20595] there should be a way to suggest that `auto` return will only be of certain types

2023-10-24 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=20595 Basile-z changed: What|Removed |Added See Also||https://issues.dlang.org/sh |

[Issue 21434] Download files are not deleted when successfully installed with auto update.

2023-10-18 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=21434 --- Comment #1 from dlangBugzillaToGithub --- THIS ISSUE HAS BEEN MOVED TO GITHUB https://github.com/dlang/visuald/issues/254 DO NOT COMMENT HERE ANYMORE, NOBODY WILL SEE IT, THIS ISSUE HAS BEEN MOVED TO GITHUB --

[Issue 16194] auto return type inference depends on return statement order

2023-10-09 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16194 RazvanN changed: What|Removed |Added CC||snarwin+bugzi...@gmail.com --- Comment #3 from

[Issue 23933] auto return type disables DIP1000 scope check

2023-05-24 Thread d-bugmail--- via Digitalmars-d-bugs
||alphaglosi...@gmail.com Resolution|--- |INVALID --- Comment #4 from Richard Cattermole --- The inference can be seen when you use auto instead of scope inside of safeUsage when you output the AST. ```d struct Struct { int* p

[Issue 23933] auto return type disables DIP1000 scope check

2023-05-24 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=23933 --- Comment #3 from RazvanN --- So, if we enable attribute inference for all functions that have a body, this will be fixed as a consequence. Or, the workaround would be to manually annotate `hmm` as scope. --

[Issue 23933] auto return type disables DIP1000 scope check

2023-05-24 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=23933 --- Comment #2 from RazvanN --- [...] for auto functions because a function body needs to be present* --

[Issue 23933] auto return type disables DIP1000 scope check

2023-05-24 Thread d-bugmail--- via Digitalmars-d-bugs
RazvanN --- Under the current specification this is not a bug, even though the behavior is surprising. Attributes are inferred for auto functions because you a function body needs to be present. Attributes are not inferred for non-auto functions, even if the body is present. --

[Issue 23933] auto return type disables DIP1000 scope check

2023-05-24 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=23933 Atila Neves changed: What|Removed |Added Keywords||accepts-invalid, safe --

[Issue 23933] New: auto return type disables DIP1000 scope check

2023-05-24 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=23933 Issue ID: 23933 Summary: auto return type disables DIP1000 scope check Product: D Version: D2 Hardware: x86_64 OS: Linux Status: NEW Severity: normal

[Issue 23914] "auto ref" resolution on return value prevented by noreturn (bottom type)

2023-05-19 Thread d-bugmail--- via Digitalmars-d-bugs
|--- |FIXED --- Comment #4 from Dlang Bot --- dlang/dmd pull request #15240 "Fix Issue 23914 - auto ref resolution on return value prevented by noreturn" was merged into master: - 883de397fb3a1405bdfaaa985abc905049c41fb0 by RazvanN7: Fix Issue 23914 - auto ref resolution on re

[Issue 23873] [ICE] segfault on imported `static if ; else auto x`

2023-05-16 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=23873 --- Comment #3 from Dlang Bot --- dlang/dmd pull request #15238 "merge stable" was merged into master: - c2f8f32de55ec635e65d8451a6a805f2f3ac5b2f by Razvan Nitu: Fix Issue 23873 - [ICE] segfault on imported static if ; else auto x (#151

[Issue 23914] "auto ref" resolution on return value prevented by noreturn (bottom type)

2023-05-16 Thread d-bugmail--- via Digitalmars-d-bugs
--- @RazvanN7 created dlang/dmd pull request #15240 "Fix Issue 23914 - auto ref resolution on return value prevented by noreturn" fixing this issue: - Fix Issue 23914 - auto ref resolution on return value prevented by noreturn https://github.com/dlang/dmd/pull/15240 --

[Issue 23917] "ref" in alias this call not detected in "auto ref" return resolution

2023-05-12 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=23917 --- Comment #2 from Vladimir Panteleev --- (Oops, ignore above comment, got my return types mixed up.) --

[Issue 23917] "ref" in alias this call not detected in "auto ref" return resolution

2023-05-12 Thread d-bugmail--- via Digitalmars-d-bugs
! / test.d struct NC { @disable this(this); } struct A { @property ref NC value() { assert(false); } alias value this; } A a; ref NC f1(ref return NC value) { return value; } auto ref NC get1() { return f1(a); } // OK ref T f2(T)(ref return T value) { return value; } auto

[Issue 23917] New: "ref" in alias this call not detected in "auto ref" return resolution

2023-05-12 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=23917 Issue ID: 23917 Summary: "ref" in alias this call not detected in "auto ref" return resolution Product: D Version: D2 Hardware: All OS: Al

[Issue 23914] "auto ref" resolution on return value prevented by noreturn (bottom type)

2023-05-12 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=23914 Vladimir Panteleev changed: What|Removed |Added Summary|"auto ref" resolution |"auto

[Issue 23914] "auto ref" resolution prevented by bottom type

2023-05-12 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=23914 --- Comment #2 from Vladimir Panteleev --- No. --

[Issue 23914] "auto ref" resolution prevented by bottom type

2023-05-12 Thread d-bugmail--- via Digitalmars-d-bugs
`auto ref` for template function parameters only? --

[Issue 23914] "auto ref" resolution prevented by bottom type

2023-05-12 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=23914 Vladimir Panteleev changed: What|Removed |Added Summary|"auto ref" determination|"auto

[Issue 23914] New: "auto ref" determination prevented by bottom type

2023-05-12 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=23914 Issue ID: 23914 Summary: "auto ref" determination prevented by bottom type Product: D Version: D2 Hardware: All OS: All Status: NEW Severi

[Issue 18151] wrong auto ref lvalue inference for implicitly converted alias this parameters

2023-05-09 Thread d-bugmail--- via Digitalmars-d-bugs
--- @RazvanN7 created dlang/dmd pull request #15214 "Fix Issue 18151 - wrong auto ref lvalue inference for implicitly converted alias this parameters" fixing this issue: - Fix Issue 18151 - wrong auto ref lvalue inference for implicitly converted alias this parameters https://github.com/dlang/dmd/pull/15214 --

[Issue 23873] [ICE] segfault on imported `static if ; else auto x`

2023-05-03 Thread d-bugmail--- via Digitalmars-d-bugs
|--- |FIXED --- Comment #2 from Dlang Bot --- dlang/dmd pull request #15168 "Fix Issue 23873 - [ICE] segfault on imported static if ; else auto x" was merged into stable: - e6c2ecf729a84e38e6746ad23bfa9ecd0d38491c by RazvanN7: Fix Issue 23873 - [ICE] segfault on imported static

[Issue 23873] [ICE] segfault on imported `static if ; else auto x`

2023-05-02 Thread d-bugmail--- via Digitalmars-d-bugs
--- @RazvanN7 created dlang/dmd pull request #15168 "Fix Issue 23873 - [ICE] segfault on imported static if ; else auto x" fixing this issue: - Fix Issue 23873 - [ICE] segfault on imported static if ; else auto x https://github.com/dlang/dmd/pull/15168 --

[Issue 23873] [ICE] segfault on imported `static if ; else auto x`

2023-05-02 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=23873 RazvanN changed: What|Removed |Added Keywords||ice CC|

[Issue 23873] New: [ICE] segfault on imported `static if ; else auto x`

2023-05-01 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=23873 Issue ID: 23873 Summary: [ICE] segfault on imported `static if ; else auto x` Product: D Version: D2 Hardware: x86_64 OS: Linux Status: NEW Severity

[Issue 23833] auto dereferncing does work with alias this

2023-04-11 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=23833 --- Comment #2 from james.g...@remss.net --- (In reply to RazvanN from comment #1) > The compiler does auto dereferencing only when the lhs of a dot expression > is a pointer to an aggregate type (struct, class, interface, union). That

[Issue 23833] auto dereferncing does work with alias this

2023-04-11 Thread d-bugmail--- via Digitalmars-d-bugs
||razvan.nitu1...@gmail.com Resolution|--- |WONTFIX --- Comment #1 from RazvanN --- The compiler does auto dereferencing only when the lhs of a dot expression is a pointer to an aggregate type (struct, class, interface, union). That does not mean

[Issue 23833] New: auto dereferncing does work with alias this

2023-04-10 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=23833 Issue ID: 23833 Summary: auto dereferncing does work with alias this Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: normal

[Issue 20595] there should be a way to suggest that `auto` return will only be of certain types

2023-03-31 Thread d-bugmail--- via Digitalmars-d-bugs
Treleaven --- You can already do this with an OutStatement with a static assert: auto f() out (r) { static assert(is(typeof(r) : int)); } do { return ""; } Compiling this you get an error, and the out contract should/could be shown in the docs (haven't checked). --

Re: 'auto' keyword

2023-03-12 Thread Ali Çehreli via Digitalmars-d-learn
On 3/12/23 06:07, DLearner wrote: > 1. As a shorthand to make the type of the variable being declared the > same as the type on the right hand side of an initial assignment. As Adam explained, D already has type inference without a special keyword. However, some places where 'auto' (or

Re: 'auto' keyword

2023-03-12 Thread kdevel via Digitalmars-d-learn
On Sunday, 12 March 2023 at 13:27:05 UTC, Adam D Ruppe wrote: [...] *any* storage class will work for type inference. [...] After heaving read [1] I immediately thought of this: void main () { deprecated i = 3; i = 4; } $ dmd test.d test.d(4): Deprecation: variable

Re: 'auto' keyword

2023-03-12 Thread Paul Backus via Digitalmars-d-learn
On Sunday, 12 March 2023 at 15:31:07 UTC, Salih Dincer wrote: Moreover, `auto ref` or `ref auto` is needed in functions. That's because `ref` isn't part of the argument or return value's type, so it isn't covered by **type** inference. Instead, D has a totally separate feature for "

Re: 'auto' keyword

2023-03-12 Thread Salih Dincer via Digitalmars-d-learn
. The auto keyword is really helpful for shortening it. But in at least 2 cases (one of which is interfaces) it should help the compiler. For example, contrary to expected, it is dynamic array: ```d auto arr = [ 1, 2, 3 ]; ``` Moreover, `auto ref` or `ref auto` is needed in functions. SDB@79

Re: 'auto' keyword

2023-03-12 Thread Adam D Ruppe via Digitalmars-d-learn
On Sunday, 12 March 2023 at 13:07:58 UTC, DLearner wrote: Is it correct that this _single_ keyword is used to indicate _two_ quite different things: No, it only actually does #2 in your thing. The type is optional meaning *any* storage class will work for type inference. `auto

'auto' keyword

2023-03-12 Thread DLearner via Digitalmars-d-learn
Is it correct that this _single_ keyword is used to indicate _two_ quite different things: 1. As a shorthand to make the type of the variable being declared the same as the type on the right hand side of an initial assignment. Example: ```auto A = 5;``` makes A an int. 2. To indicate

[Issue 23747] 'auto ref' function return signature does not flag escaping a reference to local variable

2023-02-28 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=23747 --- Comment #3 from RazvanN --- (In reply to Mike S from comment #2) > Ah noted, that is perhaps my mistake then. Looking at the specification > again with this in mind, I now see how 'auto ref' is deducing the 'refness' > of a

[Issue 23747] 'auto ref' function return signature does not flag escaping a reference to local variable

2023-02-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=23747 --- Comment #2 from Mike S --- Ah noted, that is perhaps my mistake then. Looking at the specification again with this in mind, I now see how 'auto ref' is deducing the 'refness' of a function. This means 'auto ref' snd 'ref auto' have different

[Issue 23747] 'auto ref' function return signature does not flag escaping a reference to local variable

2023-02-27 Thread d-bugmail--- via Digitalmars-d-bugs
||razvan.nitu1...@gmail.com Resolution|--- |INVALID --- Comment #1 from RazvanN --- This bug report is invalid. All of the `auto ref` functions work as expected. `Auto ref` does not mean "ref + type deduction", but rather "deduce if a func

[Issue 23747] 'auto ref' function return signature does not flag escaping a reference to local variable

2023-02-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=23747 Iain Buclaw changed: What|Removed |Added Priority|P1 |P3 --

[Issue 23747] New: 'auto ref' function return signature does not flag escaping a reference to local variable

2023-02-26 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=23747 Issue ID: 23747 Summary: 'auto ref' function return signature does not flag escaping a reference to local variable Product: D Version: D2 Hardware: x86_64 OS

[Issue 23715] compilable/testcstuff1.c:273:23: error: function-scope 'tli' implicitly auto and declared '_Thread_local'

2023-02-20 Thread d-bugmail--- via Digitalmars-d-bugs
Iain Buclaw --- (In reply to Walter Bright from comment #1) > Shouldn't _Thread_local override the auto default? It does not, and the C11 spec makes this clear: This paragraph under C11 6.2.4 - Storage durations of objects """ C11 6.2.4-5: An object whose identifier is declar

[Issue 23715] compilable/testcstuff1.c:273:23: error: function-scope 'tli' implicitly auto and declared '_Thread_local'

2023-02-19 Thread d-bugmail--- via Digitalmars-d-bugs
from Walter Bright --- Shouldn't _Thread_local override the auto default? --

[Issue 23715] compilable/testcstuff1.c:273:23: error: function-scope 'tli' implicitly auto and declared '_Thread_local'

2023-02-15 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=23715 Iain Buclaw changed: What|Removed |Added Keywords||accepts-invalid, ImportC See Also|

[Issue 23715] New: compilable/testcstuff1.c:273:23: error: function-scope 'tli' implicitly auto and declared '_Thread_local'

2023-02-15 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=23715 Issue ID: 23715 Summary: compilable/testcstuff1.c:273:23: error: function-scope 'tli' implicitly auto and declared '_Thread_local' Product: D Version: D2 Hardware: All

[Issue 20619] ddox documentation "auto auto" return values

2023-02-08 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=20619 John Hall changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Issue 15368] Improve error message for "auto" keyword inside "foreach"

2023-02-01 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15368 --- Comment #3 from Dlang Bot --- dlang/dmd pull request #14857 "merge stable" was merged into master: - 3683d2384a4eecdc2f816177a04f3a52032f8f79 by Dennis: fix 15368 - improve error message when using auto in foreach (#14839) https://

[Issue 15368] Improve error message for "auto" keyword inside "foreach"

2023-01-23 Thread d-bugmail--- via Digitalmars-d-bugs
|--- |FIXED --- Comment #2 from Dlang Bot --- dlang/dmd pull request #14839 "Fix 15368 - improve error message when using auto in foreach" was merged into stable: - e7c2729806c1e7328c736af1177b322942717f17 by Dennis Korpel: fix 15368 - improve error message when using auto in fore

[Issue 15368] Improve error message for "auto" keyword inside "foreach"

2023-01-21 Thread d-bugmail--- via Digitalmars-d-bugs
--- @dkorpel created dlang/dmd pull request #14839 "Fix 15368 - improve error message when using auto in foreach" fixing this issue: - fix 15368 - improve error message when using auto in foreach https://github.com/dlang/dmd/pull/14839 --

[Issue 14381] It is too difficult to contribute to the auto-tester

2023-01-17 Thread d-bugmail--- via Digitalmars-d-bugs
||ibuc...@gdcproject.org Resolution|--- |WONTFIX --- Comment #9 from Iain Buclaw --- The Auto-tester itself has been taken down. --

[Issue 23626] [REG2.096] Template deduction with auto const ref Args... and delegate

2023-01-15 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=23626 --- Comment #9 from Dlang Bot --- dlang/dmd pull request #14821 "follow-up Issue 23626 - invert trustSystemEqualsDefault initializer to true" was merged into master: - c111eaedcdbe6b4a7da372e2b05cca1cbac4b677 by Iain Buclaw: follow-up Issue 23626

[Issue 23626] [REG2.096] Template deduction with auto const ref Args... and delegate

2023-01-15 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=23626 --- Comment #8 from Dlang Bot --- dlang/dmd pull request #14823 "merge stable" was merged into master: - 815eb678c704470d190fc63579428d481bf55063 by Iain Buclaw: fix Issue 23626 - [REG2.096] Template deduction with auto cons

[Issue 23626] [REG2.096] Template deduction with auto const ref Args... and delegate

2023-01-15 Thread d-bugmail--- via Digitalmars-d-bugs
|--- |FIXED --- Comment #7 from Dlang Bot --- dlang/dmd pull request #14818 "fix Issue 23626 - [REG2.096] Template deduction with auto const ref Args... and delegate" was merged into stable: - ca530908ce1ce07d52f0c90aaa5f3824cbc7816e by Iain Buclaw: fix Issue 23626 - [REG2.096

[Issue 19169] [betterC] bogus TypeInfo error for `enum string[] a = ["a"]; auto aa = a;`

2023-01-14 Thread d-bugmail--- via Digitalmars-d-bugs
|--- |FIXED --- Comment #6 from Walter Bright --- (In reply to Nicholas Wilson from comment #0) > extern(C) void main() { > enum string[] a = ["a"]; > auto aa = a; // line 3 > } Now produces the error: test.d(3): Error: expression `["a"]

[Issue 23626] [REG2.096] Template deduction with auto const ref Args... and delegate

2023-01-14 Thread d-bugmail--- via Digitalmars-d-bugs
--- @ibuclaw created dlang/dmd pull request #14818 "fix Issue 23626 - [REG2.096] Template deduction with auto const ref Args... and delegate" fixing this issue: - fix Issue 23626 - [REG2.096] Template deduction with auto const ref Args... and delegate https://github.com/dlang/dmd/pull/14818 --

[Issue 23626] [REG2.096] Template deduction with auto const ref Args... and delegate

2023-01-14 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=23626 --- Comment #5 from Iain Buclaw --- Still 3 files, but one possible reduction. space_reclaimer.d ``` void __trace_maybeDumpTupleToFile(Args)(ref const Args ) { } auto as(Func)(Func) {} @nogc void foo() { } void assertOp(LHS)(LHS lhs

[Issue 23626] [REG2.096] Template deduction with auto const ref Args... and delegate

2023-01-14 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=23626 --- Comment #4 from Iain Buclaw --- (In reply to johanengelen from comment #0) > void func_2(Dlg)(Dlg dlg) { > __trace_maybeDumpTupleToFile(dlg); > } Just a suggestion, should this be `const Dlg` instead? --

[Issue 23626] [REG2.096] Template deduction with auto const ref Args... and delegate

2023-01-14 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=23626 Iain Buclaw changed: What|Removed |Added See Also||https://issues.dlang.org/sh

[Issue 23626] [REG2.096] Template deduction with auto const ref Args... and delegate

2023-01-14 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=23626 Iain Buclaw changed: What|Removed |Added CC||ibuc...@gdcproject.org See Also|

[Issue 23626] [REG2.096] Template deduction with auto const ref Args... and delegate

2023-01-14 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=23626 --- Comment #1 from johanenge...@weka.io --- This frontend change "fixes" the errors (3 lines removed): diff dmd/mtype.d: ``` /** Extends TypeNext.constConv by also checking for matching attributes **/ override MATCH constConv(Type to) {

[Issue 23626] New: [REG2.096] Template deduction with auto const ref Args... and delegate

2023-01-14 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=23626 Issue ID: 23626 Summary: [REG2.096] Template deduction with auto const ref Args... and delegate Product: D Version: D2 Hardware: All OS: All Status

[Issue 23626] [REG2.096] Template deduction with auto const ref Args... and delegate

2023-01-14 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=23626 johanenge...@weka.io changed: What|Removed |Added Keywords||industry, rejects-valid --

[Issue 18151] wrong auto ref lvalue inference for implicitly converted alias this parameters

2022-12-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=18151 Iain Buclaw changed: What|Removed |Added Priority|P3 |P2 --

[Issue 5288] auto return: forward ref error when using it with recursive functions

2022-12-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=5288 Iain Buclaw changed: What|Removed |Added Priority|P2 |P3 --

[Issue 6532] Struct within class cannot auto dereference templated methods

2022-12-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=6532 Iain Buclaw changed: What|Removed |Added Priority|P2 |P3 --

[Issue 8204] Can't instantiate auto ref template explicitly

2022-12-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=8204 Iain Buclaw changed: What|Removed |Added Priority|P2 |P3 --

[Issue 9203] Clarify that template functions with auto ref params do not share static locals

2022-12-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=9203 Iain Buclaw changed: What|Removed |Added Priority|P2 |P3 --

[Issue 10574] "auto ref" fails to match when IFTI succeeds (strip to level const)

2022-12-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=10574 Iain Buclaw changed: What|Removed |Added Priority|P2 |P3 --

[Issue 7381] Make auto tail-const

2022-12-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=7381 Iain Buclaw changed: What|Removed |Added Priority|P2 |P4 --

[Issue 5436] tightening auto decl spec

2022-12-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=5436 Iain Buclaw changed: What|Removed |Added Priority|P2 |P4 --

[Issue 9165] Auto conversion from dynamic array to fixed size array at return

2022-12-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=9165 Iain Buclaw changed: What|Removed |Added Priority|P2 |P4 --

[Issue 12488] foreach() should accept (and ignore) 'auto' in ForeachType

2022-12-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=12488 Iain Buclaw changed: What|Removed |Added Priority|P2 |P4 --

[Issue 11235] Add analog of TypeTuple that does not auto-expand

2022-12-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=11235 Iain Buclaw changed: What|Removed |Added Priority|P2 |P4 --

[Issue 4707] auto ref for foreach loops

2022-12-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=4707 Iain Buclaw changed: What|Removed |Added Priority|P2 |P4 --

[Issue 23403] Segfault when calling auto-generated struct constuctor with __FUNCTION__ or __PRETTY_FUNCTION__

2022-12-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=23403 Iain Buclaw changed: What|Removed |Added Priority|P1 |P2 --

[Issue 16041] Forward reference with auto return

2022-12-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=16041 Iain Buclaw changed: What|Removed |Added Priority|P1 |P3 --

  1   2   3   4   5   6   7   8   9   10   >