Skip to content
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

New Frontend™ progress report #124

Open
Hamcha opened this issue Sep 20, 2014 · 5 comments
Open

New Frontend™ progress report #124

Hamcha opened this issue Sep 20, 2014 · 5 comments

Comments

@Hamcha
Copy link
Member

Hamcha commented Sep 20, 2014

Since I used the Erlang frontend as an example while doing Goleg and now it's gone, I'd like to know what's needs to be done so I know what to do and when the new frontend will be ready for merging.

Missing Features

Other stuff

Tell me if I forgot something.

As I said on IRC, if you think we should edit how the API work, speak up, it's better to decide before I implement stuff.

@qpfiffer
Copy link
Member

It was never implemented in the Erlang frontend, but I'd like support for cas, too.

Edit: Another awesome thing to have would be frontend tests, we currently have none.

@Hamcha
Copy link
Member Author

Hamcha commented Sep 20, 2014

I don't know Travis' status for Go stuff, so it'd be best if you do those settings yourself, my buildbots have all Go installed, so it shouldn't be a problem. I'll see what I can do with testing…

@kyleterry
Copy link
Member

I can setup the travis stuff, I've already done it for tenyks.

@qpfiffer
Copy link
Member

Testing ticket here

@Hamcha Hamcha mentioned this issue Oct 7, 2014
@kyleterry
Copy link
Member

Now with thread safety™

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

No branches or pull requests

3 participants