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.

Sign up for GitHub

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

Jump to bottom

scope ergonomics and a ToValue overload trait #37

Closed
dherman opened this issue Jan 5, 2016 · 2 comments
Closed

scope ergonomics and a ToValue overload trait #37

dherman opened this issue Jan 5, 2016 · 2 comments
Labels
API

Comments

@dherman
Copy link
Collaborator

dherman commented Jan 5, 2016

Some suggestions from @eddyb for making Scope objects more ergonomic:

  • overloaded scope.primitive(v) to allow creating primitive JS types
  • when callability becomes overloadable, this could be scope(v)
  • look for other places to use overloading, like passing int/float/string/bool to various methods
@dherman dherman added the API label Jan 6, 2016
dherman pushed a commit that referenced this issue Sep 18, 2017
Merge pull request #37 from neon-bindings/eliminate-abi-env-variable
f415143 
Don't supply a NEON_NODE_ABI env variable
dherman pushed a commit that referenced this issue Sep 18, 2017
Roll back #37 for now. I'll file an issue to eliminate the NEON_NODE_…
061874a 
…ABI environment variable as part of the 0.2 release, whenever that happens. For now it doesn't really hurt to keep compatibility.
dherman pushed a commit that referenced this issue Sep 18, 2017
Merge pull request #41 from neon-bindings/restore-abi-env-variable
da56b39 
Roll back #37 for now
@dherman dherman mentioned this issue Sep 18, 2017
Closed
@dherman
Copy link
Collaborator Author

dherman commented Nov 17, 2017

This should be addressed by the Classes 2.0 and VM 2.0 RFCs.

@dherman dherman closed this as completed Nov 17, 2017
@divmain
Copy link
Collaborator

divmain commented Nov 17, 2017

Work tracked here:
neon-bindings/rfcs#7
neon-bindings/rfcs#6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
API
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dherman @divmain