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

RSS status? #60

Open
kach opened this issue Apr 2, 2015 · 10 comments
Open

RSS status? #60

kach opened this issue Apr 2, 2015 · 10 comments

Comments

@kach
Copy link

kach commented Apr 2, 2015

It looks like the RSS feed for this book is incomplete.

@sdiehl
Copy link
Owner

sdiehl commented Apr 6, 2015

The book itself is incomplete.

@tsuri
Copy link

tsuri commented Apr 6, 2015

I think lot of people are eagerly waiting for the book to be more complete.
I really hope you'll find the time to work on it, as many of the topics
you're planning to cover cannot be easily found elsewhere (and in general
are rather deeply embedded in source code rather than being explained in
the way you do)

Maurizio

On Mon, Apr 6, 2015 at 8:47 AM, Stephen Diehl [email protected]
wrote:

The book itself is incomplete.


Reply to this email directly or view it on GitHub
#60 (comment)
.

@sdiehl
Copy link
Owner

sdiehl commented Apr 6, 2015

Thanks for the kind words. I do very much intend to finish the book, although I think the timeline might be closer to the end of the year for completion.

@kach
Copy link
Author

kach commented Apr 6, 2015

Ah, I see, I was confused because the chapters were listed in the index but did not appear on my RSS reader. Sorry for the trouble.

P.S. Your section on Hindley-Milner inference saved me hours of trouble—thank you very much for writing that. In particular, your quick listing of all the notation used was extremely helpful, and I think more books should do this.

One comment, though: your convention for the substitution operation appears to differ from the one used in the book Functional Programming (Field and Harrison, 1989). The order of the arguments, as in [a/b] vs [b/a], is reversed in the book.

One last thing—I found the diagrams in these slides very helpful to understanding the algorithm: http://www.cs.colorado.edu/~bec/courses/csci5535-s09/slides/ML_Type_Inference_and_Unification.pdf Perhaps they may interest you. :-)

@tommythorn
Copy link
Contributor

My $0.02: The conventional usage in academia is to write new/old, e.g. e1[e2/x]. The intuition behind this is the analogy with division ("Dividing out the x, replacing with e2").

@sdiehl
Copy link
Owner

sdiehl commented Apr 6, 2015

@Hardmath123 @tommythorn I debated this for a while, TAPL also uses the reveres notation. Is there a consensus among the people following this about which is preferable?

@kach
Copy link
Author

kach commented Apr 6, 2015

To me personally, your convention is more "obvious" because it is reminiscent of sed-style text replacement.

@sdiehl
Copy link
Owner

sdiehl commented Apr 6, 2015

@Hardmath123 That was my reasoning too.

@tommythorn
Copy link
Contributor

I obviously think you should stay with the convention in the relevant literature, but failing that, maybe instead use a different notation, say e1[x → e2] so there's no ambiguity.

@tommythorn
Copy link
Contributor

Is there a place to debate/ask questions about the implementation/book? (This obviously isn't, but the issue has already strayed from the original RSS)

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

No branches or pull requests

4 participants