Skip to content

Conversation

HaraldJoerg
Copy link

I am very much interested in named parameters and only yesterday
started a new project... which will now use the signature-named-parameters branch, because of why not.

One of my first quick attempts hit a weird way where it goes wrong.

This signature lacks a comma between the parameters:

sub core (:$id :$type) {
    ...
}

Running it through the Perl interpreter which understands named parameter segfaults.
I found equivalent tests for positional parameters in t/op/signatures.t. Maybe the different path to parse named parameters should get its own test?

The error message in the test is just a guess and might need adjustment...

  • This set of changes does not require a perldelta entry.

leonerd and others added 2 commits August 28, 2025 11:27
t/op/signatures.t (t096_named): A syntax error with named parameters
A very similar test with positional parameters is in t096, I *guess*
the same error message should appear for named parameters
@leonerd leonerd force-pushed the signature-named-parameters branch 3 times, most recently from dcdbe8c to 52ccfb0 Compare September 18, 2025 18:04
@leonerd leonerd force-pushed the signature-named-parameters branch 5 times, most recently from c495ed3 to a009c2c Compare September 26, 2025 10:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants