Sean T Allen

@erdman I left some comments. I think you have the basis of a very good pattern here. Keep going!

I do not think libuv is the right approach for us. I think something along the lines of Erlang's "dirty schedulers" would be the correct approach. I reserve the right...

Leaving aside the "how do we know something will block". I think what we would want is... - normal scheduler behavior for "non-blocking" calls - we have a pool of...

FYI there's a String RFC that is being worked on so anyone interested in this might want to check that out: https://github.com/ponylang/rfcs/pull/179

I'm going to try doing a modification to a source file and see how I feel about `this.`. I'm not a fan of `@` as it breaks FFI (if it...

I'm wary of a symbol for "self" access. Especially as we already have `this`. I tried out `this.` on a couple different bits of code I had written and it...

I appear to be an incrementalist at the moment. I find myself not in favor of adding a new symbol __at this time__. And rather only want consider the explicit...

I have a question for folks, please respond directly on this comment with thumbs up/thumbs down reaction (and not adding additional comments for now that bust up the flow of...

I'm not in favor of new methods. I'd rather use existing failure methods that already exist. We are pre-1.0, this is a small change, backwards compatibility isn't a concern.

The "How we teach this" depends on functionality that doesn't exist... deprecation annotation. So, I don't consider that to be a good answer. I think it would be reasonable to...