ES5 => ES6

[davidchambers]

Valued members of the Sanctuary community, I request your input.

I remain pleased with our decision not to require any build tools to publish this project. Our approach is simply to wait for a language feature to become universally supported before adopting it.

Sanctuary currently targets ES5. I ❤️ one feature added to the language in ES6: x => x. I look forward to using arrow function expressions in the Sanctuary codebase, but only once this imposes no burden on those who depend on Sanctuary.

Has the time come for Sanctuary to adopt arrow function expressions? Help us to decide by sharing your reaction!

• 🚀 This would not be a problem for me as I already target ES6 (or later).
• 👍 ES5 compatibility is important to me but I am happy to transpile dependencies to ES5.
• 👎 ES5 compatibility is important to me and I want to keep my deployment process simple.

[davidchambers]

This took a little longer than expected. 🙈