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

Migrate to DLR #16

Open
ForNeVeR opened this issue Mar 12, 2014 · 3 comments
Open

Migrate to DLR #16

ForNeVeR opened this issue Mar 12, 2014 · 3 comments

Comments

@ForNeVeR
Copy link
Member

We should integrate the DLR support into our project.

Our attempt to make a statically typed LISP was doomed to failure from the very beginning.

Our LISP dialect should be a dynamically typed but should try to benefit from the compile-time (and runtime) type knowledge when possible (I hope the DLR will help us with that).

@hagane
Copy link
Contributor

hagane commented Mar 12, 2014

Well, I personally blame naive backend implementation. But yes, staticity, especially trying to infer function signature from it's usage did played a major part, so a major rethinking and redesign is in order. Though, I'm in favor of scrapping the source entirely and starting from scratch.

@ForNeVeR
Copy link
Member Author

Though, I'm in favor of scrapping the source entirely and starting from scratch.

Agreed.

Currently I'm reading about the DLR and what it can offer for us, and after that I'll try to summarize and make a plan for our next steps.

@hagane
Copy link
Contributor

hagane commented Mar 12, 2014

So, looks like everyone is in favor. I'll go purge some source then.

@ForNeVeR ForNeVeR added this to the Alpha milestone Mar 14, 2014
@ForNeVeR ForNeVeR self-assigned this Mar 14, 2014
@ForNeVeR ForNeVeR removed their assignment Dec 26, 2015
@ForNeVeR ForNeVeR removed this from the Alpha milestone Apr 3, 2016
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

2 participants