Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error message complains too much about Metamodel.nqp (Buf.new('0')) #5977

Open
p6rt opened this issue Jan 4, 2017 · 3 comments
Open

error message complains too much about Metamodel.nqp (Buf.new('0')) #5977

p6rt opened this issue Jan 4, 2017 · 3 comments
Labels

Comments

@p6rt
Copy link

@p6rt p6rt commented Jan 4, 2017

Migrated from rt.perl.org#130502 (status was 'open')

Searchable as RT130502$

@p6rt

This comment has been minimized.

Copy link
Author

@p6rt p6rt commented Jan 4, 2017

From @AlexDaniel

Code​:
say Buf.new('0')

Result​:
Type check failed in initializing element #​0 to Buf; expected uint8 but got Str ("0")
  in any at gen/moar/Metamodel.nqp line 1727
  in block <unit> at /tmp/9PmeQTevmg line 1

Actually thrown at​:
  in any at gen/moar/Metamodel.nqp line 3072
  in any at gen/moar/Metamodel.nqp line 1727
in block <unit> at /tmp/9PmeQTevmg line 1

It points three times to a line in Metamodel.nqp, and only once to the actual user file. Perhaps there is a way to improve it? Maybe not just for this case, but for any exception?

@p6rt

This comment has been minimized.

Copy link
Author

@p6rt p6rt commented Mar 10, 2018

From @dogbert17

On Wed, 04 Jan 2017 14​:21​:15 -0800, alex.jakimenko@​gmail.com wrote​:

Code​:
say Buf.new('0')

Result​:
Type check failed in initializing element #​0 to Buf; expected uint8
but got Str ("0")
in any at gen/moar/Metamodel.nqp line 1727
in block <unit> at /tmp/9PmeQTevmg line 1

Actually thrown at​:
in any at gen/moar/Metamodel.nqp line 3072
in any at gen/moar/Metamodel.nqp line 1727
in block <unit> at /tmp/9PmeQTevmg line 1

Fixed with commit rakudo/rakudo@f230224

It points three times to a line in Metamodel.nqp, and only once to the
actual user file. Perhaps there is a way to improve it? Maybe not just
for this case, but for any exception?

@p6rt

This comment has been minimized.

Copy link
Author

@p6rt p6rt commented Mar 10, 2018

The RT System itself - Status changed from 'new' to 'open'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.