Handling "lock" statement in any reasonable manner #777

Closed
DaniilVeriga opened this Issue Dec 22, 2015 · 1 comment

Projects

None yet

3 participants

@DaniilVeriga
Contributor

http://forums.bridge.net/forum/general/open-discussions/1320

The "lock" statement appears frequently in any multithreaded C# code. While it doesn't make sense in a browser it would be helpful if it came up as a warning instead of an error and was simply ignored.

@vladsch vladsch added a commit that referenced this issue Jan 26, 2016
@vladsch vladsch [TEST] [#777] Update unit tests cac9d01
@vladsch vladsch added this to the 1.11 milestone Jan 26, 2016
@DaniilVeriga
Contributor

Just a clarification on what was actually done. Now the lock statement is just ignored in the emitted JavaScript code. All what is inside is emitted.
Live Sample

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment