[Issue 10848] Compiler should always try to inlining a direct lambda call

d-bugmail at puremagic.com d-bugmail at puremagic.com
Mon Aug 19 20:47:43 PDT 2013


http://d.puremagic.com/issues/show_bug.cgi?id=10848



--- Comment #4 from Kenji Hara <k.hara.pg at gmail.com> 2013-08-19 20:47:41 PDT ---
(In reply to comment #1)
> Sounds like a good case for a __forceinline attribute, and then apply it
> implicitly in this case. This situation could leverage the same internal
> mechanic.

"forceinline" is misleading word.

This proposal *does not* guarantee that the generated code is always inlined.
If the given lambda body is too large/complex, or compiler's inlining ability
is very little, the generated code may not be inlined. The language spec should
allow it.

> I still have MANY places where I want to guarantee inlining of certain
> functions.

Inlining would increase compilation time. Such places should be defined
carefully.

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------


More information about the Digitalmars-d-bugs mailing list