On Sunday, 2 October 2016 at 12:27:23 UTC, Andrei Alexandrescu
wrote:
Yes, Stefan it would be terrific if you could keep an eye on it
while working on the engine. A file with properly handed
dependencies could serve as instantiation cache and save a ton
of re-instantiation waste. Thanks! --
Unexpected auto-concatenation of string elements:
string[] arr = ["a", "b" "c"];// ["a", "bc"], length==2
int[] arr2 = [[1], [2] [3]];// Error: array index 3 is out
of bounds [2][0 .. 1]
// Error: array index 3 is out
of bounds [0..1]
dmd
On 2016-10-03 12:36, Chris wrote:
Is this the preferred logging module for vibe.d:
http://vibed.org/api/vibe.core.log/
There is also:
http://vibed.org/api/vibe.http.log/
which is there for backwards compatibility?
The second one is specific for HTTP. The first one is generic.
--
/Jacob
On 2016-10-01 22:57, Martin Nowak wrote:
Please report any bugs at https://issues.dlang.org
std.process is pretty broken on macOS:
https://issues.dlang.org/show_bug.cgi?id=16580
--
/Jacob Carlborg
https://issues.dlang.org/show_bug.cgi?id=16580
--- Comment #1 from Jacob Carlborg ---
I should add that this will most likely affect any function inside std.process
that calls "environ".
--
https://issues.dlang.org/show_bug.cgi?id=16580
Issue ID: 16580
Summary: [REG 2.072.0-b1] spawnShell segfaults on macOS
Product: D
Version: D2
Hardware: x86
OS: Mac OS X
Status: NEW
Severity: regression
Is this the preferred logging module for vibe.d:
http://vibed.org/api/vibe.core.log/
There is also:
http://vibed.org/api/vibe.http.log/
which is there for backwards compatibility?
https://issues.dlang.org/show_bug.cgi?id=15306
--- Comment #6 from anonymous4 ---
How about const qualifier?
void f()
{
int i = 42;
auto dg = delegate void() const { i=0; }; //ok?
}
--
https://issues.dlang.org/show_bug.cgi?id=16265
--- Comment #1 from anonymous4 ---
But you will still have a cycle when compiling unittests? Then unittest
dependencies can't be possibly ignored.
--
https://issues.dlang.org/show_bug.cgi?id=16572
--- Comment #2 from anonymous4 ---
A small interaction between contravariance and inout here:
inout(A) f(inout B b) inout;
If you resolve the type as A delegate(B) you can't pass const(B) as argument.
--
If it's heap corruption, GC has debugging option -debug=SENTINEL
- for buffer overrun checks. Also that particular stack trace
shows that object being destroyed is allocated in bin 512, i.e.
its size is between 256 and 512 bytes.
On Sunday, October 02, 2016 18:31:11 Mike Bierlee via Digitalmars-d-learn
wrote:
> Consider the following code:
>
> enum StringTypeEnumOne : string {
> bla = "bla"
> }
>
> enum StringTypeEnumTwo : string {
> bleh = "bleh"
> }
>
> enum IntTypeEnumOne : int {
> bla = 1
> }
>
> enum
On Sunday, 25 September 2016 at 16:23:11 UTC, Matthias Klumpp
wrote:
For Ubuntu, some modifications on the code were needed, and
apparently for them the code is currently crashing in the GC
collection thread: http://paste.debian.net/840490/
Oh, wait, what do you mean by crashing?
On Sunday, 2 October 2016 at 21:05:25 UTC, A D dev wrote:
One last point:
If that was always the behavior (in all versions from 2010 - or
earlier), i.e. -o- generates neither .OBJ nor .EXE, then what
is the purpose of the option? does it act as just a syntax
check?
Purpose is to skip code
On 2016-09-27 22:21, Jacob Carlborg wrote:
I'm working on a Ddoc theme and I have trouble figuring out when the
DDOC_KEYWORD and DDOC_TEMPLATE_PARAM macros are used. Are the compiler
outputting them or should the developer be using those directly? If the
compiler is outputting them, then when is
On Saturday, 1 October 2016 at 00:06:05 UTC, Matthias Klumpp
wrote:
I do none of those things in my code though...
`grep "~this" *.d` gives nothing? It can be a struct with
destructor stored in a class. Can you observe the error? Try to
set a breakpoint at onInvalidMemoryOperationError
https://issues.dlang.org/show_bug.cgi?id=16579
Iain Buclaw changed:
What|Removed |Added
CC||ibuc...@gdcproject.org
https://issues.dlang.org/show_bug.cgi?id=16579
Issue ID: 16579
Summary: ReturnStatement[CallExp(DotVarExp)]: Corrupted runtime
on missed manifest constant propagation
Product: D
Version: D2
Hardware: All
OS:
On Sunday, 2 October 2016 at 17:22:57 UTC, Basile B. wrote:
On Sunday, 2 October 2016 at 15:54:38 UTC, Satoshi wrote:
Hello,
why
pure @safe nothrow @nogc struct Point {
}
isn't same as
struct Point {
pure: @safe: nothrow: @nogc:
}
??
This is not specified but attributes aren't applied to
On Monday, 3 October 2016 at 02:47:09 UTC, Manu wrote:
On 3 October 2016 at 02:37, Timon Gehr via Digitalmars-d
This is a known issue:
https://issues.dlang.org/show_bug.cgi?id=3720
(What I do is: typeof((this).f) is int delegate(), but
auto x =
does not compile as the 'this' reference is
On 3 October 2016 at 17:18, Jacob Carlborg via Digitalmars-d
wrote:
> On 2016-10-03 05:06, Manu via Digitalmars-d wrote:
>
>> Okay, well my current project is blocked on this. I can't progress.
>> https://issues.dlang.org/show_bug.cgi?id=16572
>
>
> I You can remove
On 2016-10-03 05:06, Manu via Digitalmars-d wrote:
Okay, well my current project is blocked on this. I can't progress.
https://issues.dlang.org/show_bug.cgi?id=16572
I You can remove "inout" ;)
--
/Jacob Carlborg
101 - 122 of 122 matches
Mail list logo