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

Make AnyVals Easier To Use #9504

Open
scabug opened this issue Oct 5, 2015 · 1 comment
Open

Make AnyVals Easier To Use #9504

scabug opened this issue Oct 5, 2015 · 1 comment

Comments

@scabug
Copy link

@scabug scabug commented Oct 5, 2015

Proposal: Add a compiler flag that makes it easier to know when an AnyVal allocation occurs.

AnyVals can radically improve performance, but allocations can occur in surprising places (removing any performance gains). SIP-15 documents the conditions under which allocation occurs, but that can be hard to remember when browsing a complicated program. Compiler support for detecting allocations would help a lot.

A couple of possible flags are:

  • Warning - Generate a compiler warning when a use-site will require an AnyVal to be allocated.
  • Throw on Allocate - Add a flag that causes an exception to be thrown when an AnyVal is allocated. The resulting stack trace should allow the programmer to track down the allocation easily.
@scabug

This comment has been minimized.

Copy link
Author

@scabug scabug commented Oct 5, 2015

Imported From: https://issues.scala-lang.org/browse/SI-9504?orig=1
Reporter: Justin Bailey (m4dc4p)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.