flow-comprehensions
flow-comprehensions copied to clipboard
cvogt
Work in progress: Simpler and more powerful alternative to Scala's built-in for-comprehension syntax
related work
Ha, looks like other people had similar ideas in the past: https://www.google.com/url?sa=t&source=web&rct=j&url=http://www.cl.cam.ac.uk/~dao29/drafts/codo-notation-orchard12.pdf&ved=0CB8QFjABahUKEwiqlr_xk-3IAhXGpB4KHfABDxY&usg=AFQjCNGgNwAa-zP749_cJ8btZS41MS_pEQ&sig2=m7OAfEFQf4CmFPwUa_UjLQ
``` [info] Compiling 5 Scala sources to /home/jilen/workspace/flow-comprehensions-example/target/scala-2.11/classes... [error] /home/jilen/workspace/flow-comprehensions-example/Flat.scala:18: exception during macro expansion: [error] java.lang.NullPointerException [error] at scala.reflect.internal.Types$$anonfun$47.apply(Types.scala:4576) [error] at scala.reflect.internal.Types$$anonfun$47.apply(Types.scala:4576) [error] at scala.reflect.internal.tpe.TypeComparers$class.isSubType1(TypeComparers.scala:319) [error] at scala.reflect.internal.tpe.TypeComparers$class.isSubType(TypeComparers.scala:278) [error] at...
Lets see if we withstand a test along these lines https://github.com/scala/pickling/issues/329
revisit optional context parameter with implicit and if there are weird type errors, when trying to use .apply on anything else and if there is a way to work around...
the common Monad.sequence has well defined semantics among others not being sequential. The comprehension currently called `sequence` in here is sequential, so we should probably rename it. How about `comprehension`...
Also see http://blog.sigfpe.com/2007/02/monads-for-vector-spaces-probability.html?showComment=1175687820000#c4694577454250958561