Hacker News new | past | comments | ask | show | jobs | submit login

Just looking at the code I came to the conclusion it had to work that way, I don't like it, way too easy to break and some people are going to be very confused when things goes wrong. It's a uncommon/unfamiliar coding constraint. If you have to declare them all in the same order every time, you might as well force a single state (like the setState API) and/or keyed state values and have a safe API.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: