On Saturday, 2 October 2021 at 13:26:27 UTC, Adam D Ruppe wrote:

so why this? it seems to take a long time from the last import xxx semantic3 xxx to reach this

inline scan grasshopper
inlined std.datetime.systime.SysTime._timezone =>
std.datetime.systime.SysTime.opAssign!().opAssign
inlined std.datetime.systime.SysTime._timezone =>
std.datetime.systime.SysTime.opAssign!().opAssign

can not be avoided? i need only till semantic, no care in inline et cetera

Do you have optimizations turned on? i.e. are you compiling with -O by accident?

On Saturday, 2 October 2021 at 16:57:48 UTC, max haughton wrote:

Not needed, it's declared:

pragma(inline, true) @property _timezone() @safe const pure nothrow @nogc

DMD does inlining in the frontend, and without the -inline flag it still inlines functions when requested by pragma(inline, true). That's why you see it logged even without codegen or -inline.

That's not what causes the long compile time though, dmd -v logs passes before doing them, not after, so it's the semantic3 before the inline pass that's taking all the time.

On Saturday, 2 October 2021 at 18:05:06 UTC, Dennis wrote:

pragma(inline, true) @property _timezone() @safe const pure nothrow @nogc

I was aware (and am not a fan of) inlining in the frontend, but didn't look at the Phobos code.

Honestly dmd shouldn't have an optimizer IMO, it's not fit for purpose anymore, if you want optimizations use GDC or LDC. Inlining doesn't even respect the semantics of the language IIRC