Groovy DevCon 7

...

• generators / for comprehensions / continuation-passing /  etc brainstorming
  • also see Tim's stream: http://blog.bloidonia.com/post/22117894718/groovy-stream-a-lazy-generator-class-for-groovy
    • might be nice as a contribution module, if we get some way of distributing some modules
  • but wait for JDK 8 new lazy stuff to mature to avoid reinventing the wheel or having two different implementations and notations for the same thing
  • but we can play with some experimental extension module

...

def fib = { 
    def state = [a:0, b:1 ]
    state.with {
        [
            next: {
                (a,b) = [b, a+b]
                a
            },
            hasNext: {
                b<100
            }
        ] as Iterator
    }
}
for (x in fib()) { println x }

• Groovy module contributions
  
  • how to share and reuse contributed modules easily
  • discuss with the Grails team to see how they're handling their plugins portal
    
    • and see how Andres is handling that within Griffon
    • Gradle is also interested in some Gradle plugins portal
    • is there some common base or collaboration possible that would suit everybody?
  • things to consider
    
    • a module should be one @Grab away
      
      • somehow uploaded to Maven Central?
      • is there a way to reuse the Groovy Modules Codehaus project
    • perhaps some modules can be part of the distribution
      
      • but if yes, what are the criteria
    • how to assert that modules work with various Groovy versions
      
      • and how to ensure that a new Groovy version doesn't break modules
      • some CI solution?
    • how to deal with sources? github vs codehaus groovy modules repo
    • nice gradle template build that would care of the uploading to Codehaus Groovy Modules
      • that could also test with various groovy versions
      • contributors can have their repositories anywhere