When you work at only one level of abstraction, current type systems are already great. When you work at several levels of abstractions... they mostly don't even try yet.
-
-
-
This Tweet is unavailable.
-
Abstraction is not multistage, though it can be supported by it — or, mostly, fail to be. Levels of abstraction handle new aspects. Most parts can and should be automatically lifted; but that requires syntactic overhaul AND cumbersome dependent types, themselves unsupported.
1 reply 0 retweets 1 like -
Replying to @Ngnghm @Iceland_jack
Aspects introduced may include concurrency, memory allocation (linearity), error reporting, persistence, access control, logging. Suddenly none of your functions are pure anymore and you live in either dynamic types or lifting hell.
4 replies 0 retweets 1 like -
Replying to @Ngnghm @Iceland_jack
Are you using “aspects” in the technical sense from the AOP community?
1 reply 0 retweets 0 likes -
Replying to @Blaisorblade @Iceland_jack
In a more technical sense maybe. See my thesis about AOP and much more: http://j.mp/FarePhD
1 reply 0 retweets 1 like -
Replying to @Ngnghm @Iceland_jack
Your thesis *draft* you mean? It’d be clearer if you mark it as such clearly on page *1*, not *11* (no I’m not going to read this in order, and I shouldn’t have to).
1 reply 0 retweets 0 likes -
Replying to @Blaisorblade @Iceland_jack
Apologies, will amend immediately.
1 reply 0 retweets 1 like
That was clear on the front page in French, now it's clearer in both languages.
-
-
Replying to @Ngnghm @Iceland_jack
Thanks for clearing that up, and good luck with your writing and defense... I'm taking a look.
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.
Read my blog!