Write for the _other_ audience. There's constantly new people coming in and that haven't heard before. That's also why we rerun talks at conferences or always have some basic ones.
-
-
-
Absolutely. But at some point, if it's not a thing academia (and hence my employer) values, there's a limit to how much I'm willing to do.
- 4 more replies
New conversation -
-
-
If any of them can be phrased as "here's this thing I would love to see an example of in Idris" I know at least one person who would love taking a crack at them. And I can't imagine just writing what's needed for that would take very long.
-
It's typically things where were too advanced for the book, but not original enough to be papers. For example, termination proofs or more detail on views.
End of conversation
New conversation -
-
-
I will probably do so for extensible records, but I will target engineering conference, not academic ones, and thus will probably not detail the results.
-
That'd be great!
- 1 more reply
New conversation -
-
-
Please, write down the stuff that does not get published because ‘everybody knows it’; the stuff that only propagates via physical proximity; the stuff that makes type theory an oral tradition. Please.
-
Yes! This! I only know about 'semantic type checking' thanks to
@jonsterling telling me and@dannygratzer's repository: https://github.com/jozefg/nbe-for-mltt … - these kinds of ideas are super valuable for those of us interested in language development outside of academia! :) - 4 more replies
New conversation -
-
-
JFP publishes tutorial papers. Here's an example that I just happen to have handy: http://www.cs.nott.ac.uk/~pszgmh/fold.pdf … :-)
-
Peter Thiemann is handling editor, and would love to hear proposals!
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.