strip minor improvement

[ringabout]

No description provided.

[juancarlospaco]

{.noinit.} ?.

[timotheecour]

@juancarlospaco

{.noinit.} ?.

where?

[juancarlospaco]

Without {.noinit.} it implicitly injects result = "" , on the proc as procedure pragma (this wont change with danger).
I use it a lot, is safe if your proc assigns to result directly and explicitly, correct me if I am wrong.

And if it does not work, then better we discovered a Bug on the pragma. 🤷

[timotheecour]

Without {.noinit.} it implicitly injects result = "" , on the proc as procedure pragma (this wont change with danger).

I suspected that's what you mean; note that this affects a large percentage of procs and there's no reason to single strip out; IMO there's a better approach than annotating each proc individually, compiler can/should do this automatically when safe to do so. Let's discuss this in another dedicated issue, it's an important one.

links

• search for RVO/NRVO
• refs: https://forum.nim-lang.org/t/4041#25251
• RVO not exception safe #14126 (comment) very relevant

[juancarlospaco]

When return is a concrete primitive type, not auto, and func is single line should be easy to just inject the noinit.
Nim does this even when result is directly assigned a static value.