Boris Carvajal
Boris Carvajal
> That zstd btw, how did you do that part? Another library import on top of it? I hear some linux distros are moving to it so I kinda wanna...
This still fails: ```d const class C {} // or immutable Array!C ac; ``` in fact this has always failed: ```d class C {} Array!(const C) ac; ``` I don't...
There is already `-vcg-ast`, what about using `-vcg` as prefix? I suppose `cg` means code generation and these switches fall under that category.
Yes, they are just a renaming of a first enum member.
> The commit message should contain "Fix" so that the bot picks up the issue. I wanted to link it only.
> I never thought this was possible until I saw changes about this. Is this described on the spec? Do we need to change it? In any way, I think...
Checking padding of DMD sources: src/dmd/checkpadding.d: ```d import dmd.ast_node; import dmd.attrib; import dmd.aliasthis; import dmd.aggregate; import dmd.complex; import dmd.cond; import dmd.ctfeexpr; import dmd.dclass; import dmd.declaration; import dmd.denum; import dmd.dimport; import...
@WalterBright, I fixed a similar bug some time ago, a self reference got allocated in the stack but escaped to other contexts. See #13109 Maybe it's the same.
I think the fix should be in `traits.d` so that only the top level `ScopeExp` inside `traits(compiles)` gets the special treatment. Still I'm curious where this `IFTI` `ScopeExp` is actually...
`automem` fails but a pull is ready. https://github.com/atilaneves/automem/pull/61