-
Notifications
You must be signed in to change notification settings - Fork 16
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
Switch statements cause compile errors #36
Comments
ideally I'd like to keep compatibility with Javascript. Perhaps there's On Tue, Jun 21, 2011 at 5:36 AM, benekastah <
|
There's always the ruby way. That's the best variation of the switch I've used.
Then if you really need to use the fallthrough capability, you can just write your switch in pure js. |
how about
? do we want/need the colons ? On Tue, Jun 21, 2011 at 8:31 AM, benekastah <
|
Yeah, I actually kind of like the colons. It's a little more javascripty, and they help me a bit visually. |
yeah agreed. maybe we don't need the else as it doesn't add anything beyond 'default' ? On Tue, Jun 21, 2011 at 8:41 AM, benekastah <
|
True. |
ok so :
which is converted to :
On Tue, Jun 21, 2011 at 8:46 AM, benekastah <
|
And when this is fixed, it would also be nice if
break
statements aren't required. They're silly. I would like something like:Just an idea.
The text was updated successfully, but these errors were encountered: