On Saturday, 30 May 2020 at 16:14:34 UTC, Steven Schveighoffer
wrote:
This is not about const or not, it's about lifetime management.
For example, this would return a pointer to a stack frame that
is about to go away:
const(char)* foo()
{
ErrorInfo info;
return info.message;
}
I
On 5/30/20 3:00 AM, Mike Parker wrote:
The following declarations now give a deprecation warning:
```d
struct ErrorInfo {
private:
char[32] _error;
char[96] _message;
public @nogc nothrow @property:
/**
Returns the string "Missing Symbol" to indicate a symbol load
On Saturday, 30 May 2020 at 07:30:17 UTC, Max Samukha wrote:
On Saturday, 30 May 2020 at 07:00:07 UTC, Mike Parker wrote:
https://run.dlang.io/is/aOZqww
Since 2.067.1: Success and no output
Thanks, Max (and you, too, Seb). I had forgotten that
run.dlang.io supports compilers going so
On Saturday, 30 May 2020 at 07:30:17 UTC, Max Samukha wrote:
On Saturday, 30 May 2020 at 07:00:07 UTC, Mike Parker wrote:
https://run.dlang.io/is/aOZqww
Since 2.067.1: Success and no output
Thanks! I forgot that run.dlang.io supports all those old
compilers.
On Saturday, 30 May 2020 at 07:00:07 UTC, Mike Parker wrote:
The following declarations now give a deprecation warning:
```d
struct ErrorInfo {
private:
char[32] _error;
char[96] _message;
public @nogc nothrow @property:
/**
Returns the string "Missing Symbol" to indicate a
On Saturday, 30 May 2020 at 07:00:07 UTC, Mike Parker wrote:
I find it rather annoying, as I'm returning `const(char)*` and
not `char*`, but it is what it is. My question is, if I add
`return` to the function declarations, will this compile all
the way back to DMD 2.067 *without*
The following declarations now give a deprecation warning:
```d
struct ErrorInfo {
private:
char[32] _error;
char[96] _message;
public @nogc nothrow @property:
/**
Returns the string "Missing Symbol" to indicate a symbol
load failure, and
the name of a library to
