-
Notifications
You must be signed in to change notification settings - Fork 12
eschew destructuring assignment #5
Comments
This is the case for almost all fantasy-land projects. I think this should be avoided in all of them. |
@davidchambers I'll think about it, but this was ongoing work and the fact that the readability improves dramatically (for js) I do favour it. Maybe it should have been on another branch rather than a breaking change tbh. |
The right option depends on whether you intend these packages to be referenced or used. |
Sorry, I wasn't aware of this when I made the original suggestion. I guess the latest release on npm isn't this version. I have to agree though, having to remember flags is a pain. I think until node gets with the times, it's better to suffer a little readability for contributions. |
If that's the case it's probably better to branch all the repo's off to I won't get chance for sometime, so if somebody beats me to it 👍 |
sanctuary-either has been released, and relies only on language features and functions available in ES5. |
I'm not sure whether this project is intended to be used or just referenced. If the former, let's avoid language features which require
node
flags or preprocessing.The text was updated successfully, but these errors were encountered: