-
Notifications
You must be signed in to change notification settings - Fork 156
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
Status on async
/ await
straight through compilation?
#977
Comments
#836 is interesting, but has no tests. The PR should still work, since lsc doesn't move very fast. Doesn't
I only know of @summivox 's fork
I don't think that's active enough to reach such a consensus. |
Thanks for the intell @vendethiel! I've just started gathering intell on what techs to use for the nodejs part. LS is a given, even though I will most likely compile it down to JS further down the line for other developers to maintain. From what I've quickly gleaned Koa2 seems to go the I'm gonna evaluate available options a bit more before nailing down the roadmap. Thanks again! |
Tests at least. (I don't have a plan for dealing with LS documentation issues in general; the website hasn't been updated since the 1.4 release and I haven't looked into what it would take to bring it up to date.) I haven't reviewed the code in that PR yet; I'm waiting for its author to add tests and tell me that it's ready for a review, since it's been a work in progress for so long. If review turns up any issues, obviously someone will have to deal with those. |
I'm on vacation and honestly I haven't been able to spare time on this
project for quite a while.
Ryan can you take over?
On Tue, Sep 19, 2017, 13:21 Ryan Hendrickson ***@***.***> wrote:
Tests at least. (I don't have a plan for dealing with LS documentation
issues in general; the website hasn't been updated since the 1.4 release
and I haven't looked into what it would take to bring it up to date.)
I haven't reviewed the code in that PR yet; I'm waiting for its author to
add tests and tell me that it's ready for a review, since it's been a work
in progress for so long. If review turns up any issues, obviously someone
will have to deal with those.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#977 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABsEGU5CTHVcgPPzfPSbeycndoogL8mhks5skCJUgaJpZM4PcaiP>
.
--
…---
Yin Zhong
|
I don't have a lot of disposable time, myself. Someone who feels strongly about having this feature in official LiveScript should pick it up in this case. |
#978 has landed! |
I know there is a number of issues on this and related, I just post this to get a fresh up to date perspective.
I'm back to some contract nodejs-coding for the first time in a few years of mainly systems coding. Now it seems Koa and similar frameworks are established enough to be usable. So of course I want to do that. And of course I want to code in LiveScript.
So, what gives?
async
andawait
keywords come in main distro LiveScript soon?The text was updated successfully, but these errors were encountered: