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

ListMap produces incorrect exception message #6370

Closed
scabug opened this issue Sep 13, 2012 · 6 comments
Closed

ListMap produces incorrect exception message #6370

scabug opened this issue Sep 13, 2012 · 6 comments
Assignees
Milestone

Comments

@scabug
Copy link

@scabug scabug commented Sep 13, 2012

immutable.ListMap produces the wrong error message for missing keys.

For a non-empty ListMap, the apply method throws an exception for missing keys. However, this incorrectly states "empty map" instead of "key not found: z".

This bug doesn't apply to mutable.ListMap nor Map.

@scabug
Copy link
Author

@scabug scabug commented Sep 13, 2012

Imported From: https://issues.scala-lang.org/browse/SI-6370?orig=1
Reporter: Rick Beton (rickb)
Affected Versions: 2.9.1, 2.9.2
Attachments:

@scabug
Copy link
Author

@scabug scabug commented Sep 14, 2012

@gkossakowski said:
Changed priority to Major. It's not a blocker.

@scabug
Copy link
Author

@scabug scabug commented Sep 16, 2012

Rick Beton (rickb) said:
'Major will do. I'd have said 'minor', but the bug submission form only gave me one choice ('blocker').
:)

@scabug
Copy link
Author

@scabug scabug commented Jan 29, 2013

@scabug
Copy link
Author

@scabug scabug commented Feb 8, 2013

@JamesIry said:
PR closed based on discussion

@scabug
Copy link
Author

@scabug scabug commented Feb 8, 2013

@ViniciusMiana said:
New PR with fixes based on discussion at: scala/scala#2096

@scabug scabug closed this Feb 11, 2013
@scabug scabug added this to the 2.10.2-RC1 milestone Apr 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants