Collectible Card Game Headquarters

Rob Cashwalker wrote:See, there you go again... waaayy over my head. . .

if the goal is to reduce heap allocation and/or memory footprint, generators are better than arrays, lists, and other collections. generators are hard to write without a mechanism for "yielding" instead of returning a value. it is possible that generators use more CPU than collections, but this is not always true.

Rob Cashwalker wrote:. . . Though I'm not too sure we should keep adding more library requirements . . .

jendave wrote:. . . My only concern is that the java-yield jar appears to be relatively unsupported.

i chose java-yield because its API was small. except that it bundles Log4J. do you want me to look for a different one? if so please let me know what the requirements are for size and support.

jendave wrote:I tried a dryRun of the release process and there is an issue with the jyield jar. since it is a "SNAPSHOT", Maven does not want to use it as part of release. There is a workaround, but it required more attention during the release build.

please let me know if i can be of help.

Braids wrote:

Rob Cashwalker wrote:See, there you go again... waaayy over my head. . .

if the goal is to reduce heap allocation and/or memory footprint, generators are better than arrays, lists, and other collections. generators are hard to write without a mechanism for "yielding" instead of returning a value. it is possible that generators use more CPU than collections, but this is not always true.

Rob Cashwalker wrote:. . . Though I'm not too sure we should keep adding more library requirements . . .

jendave wrote:. . . My only concern is that the java-yield jar appears to be relatively unsupported.

i chose java-yield because its API was small. except that it bundles Log4J. do you want me to look for a different one? if so please let me know what the requirements are for size and support.

jendave wrote:I tried a dryRun of the release process and there is an issue with the jyield jar. since it is a "SNAPSHOT", Maven does not want to use it as part of release. There is a workaround, but it required more attention during the release build.

please let me know if i can be of help.

No worries. I modified the Maven build so it automatically accepts the SNAPSHOT dep.