by pschanely on 9/22/15, 1:14 PM with 19 comments
by gamegoblin on 9/22/15, 9:35 PM
Excuse me if this is implemented and just not in the README:
It would be super awesome if there was a type inference engine that fed into the UI to increase productivity.
For example, if I start to define a function that returns an int, when I go to write out the definition, it suggests functions to me that return ints.
Suppose I pick a function "string_length" which takes strings and returns ints. Now I continue the composition, so it suggests functions (either built-ins or user-defined) which return strings.
Suppose I pick "bool_to_string" which takes a bool and returns strings. Then to finish off the function I pick from a list of bool-returning functions, say I pick "xor".
So now with a few keypresses I have defined a function that, in C, would look like:
int foo(bool x, bool y) {
return string_length(bool_to_string(x ^ y));
}by madkangas on 9/22/15, 2:29 PM
It's purely functional and stack-based. This is a clever approach to the UI problem - how to program when you can't typeLongWords? Answer: use the stack! I expect the act of writing programs will feel a lot like using an old programmable calculator.
Really excited to see how this progresses!
PS: How do I run that demo locally?
by reilly3000 on 9/22/15, 9:12 PM
2. I would flip out even more if this UI was available for more mainstream functional languages like Haskell or Clojure. Do libraries break the process? I don't think they have to.
by V-2 on 9/22/15, 11:42 PM
by tluyben2 on 9/22/15, 9:45 PM