fix: support defaults for calls with named arguments

[Stranger6667]

Fixes #490

I see it is an ad-hoc fix to illustrate the issue. I hope that in the end we can arrive at a more fundamental fix + add some more test cases, as it looks quite fragile right now (all the string passing part)

Checklist

• I have read the contribution guidelines.
• I have added tests that prove my code works as expected.
• I have added documentation if applicable.
• I have added a migration guide if applicable.

❤️ Thank you

[coveralls]

Pull Request Test Coverage Report for Build 16098719362

Details

• 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.02%) to 22.342%

---

Totals
Change from base Build 16087646043:	0.02%
Covered Lines:	870
Relevant Lines:	3894

---

💛 - Coveralls

[Xenira]

Thank you. Yes, that string part certainly needs improvement.

Ill release this as soon as possible, as this is something fundamental going wrong here.

[Xenira]

@Stranger6667 the linked issue seems to be unrelated. Did you mean #490?

[Stranger6667]

Oh, I copy-pasted it from the template and forgot to update )

[Stranger6667]

Yes, it is #490

[Xenira]

@Stranger6667 just released the fix. Thank you!

[Stranger6667]

@Xenira Thank you so much!

I had some thoughts about the defaults and will open another issue later on.

For example, I was wondering if it is feasible to support integer literal suffixes in defaults, such as 42_usize. Right now, it is passed as a literal to the PHP side as well