David Walend

I notice you sometime show the types, but comment them out: ``` val someFuture: Future[String] = … val lifted/*: Future[Try[String]]*/ = someFuture.transform(Try(_)) ``` Why use a comment? Why not just...

Thanks. That makes some sense, but I worry that innocents might cut and paste the code, then the comment rots toward being misleading. (In my own code I put type...

> This means that global will have at most scala.concurrent.context.maxThreads + scala.concurrent.context.maxExtraThreads concurrent Threads. Would "at most scala.concurrent.context.maxThreads" (and not more) be better? Will people find scala.concurrent.context.maxExtraThreads? Will they be...

Definitely. Also, if you write something that reads as strangely as "...maxExtraThreads" , revisit the config code. (Maybe even "maxIOBlockedThreads" would be better. API control would be better than properties.)

ExecutionContext.global I suppose. The harder question - what could turning the knobs actually do?

Classic awful mutable globally accessible state. They'd fight it out. Last in wins. And changes to the ExecutionContext.global doddle behind, trying to keep up. It'd be like one of those...

Thanks. Sounds good for now. --- For posterity -- I was able to put a {package somepackage} at the top of a HelloFromPackage.scalatex file, and then scala> import scalatex.somepackage.HelloFromPackage import...

I hacked around it with (the only) lump of Java code in SHRINE. It'll likely work for Java through JDK10 and maybe JDK11, but the folks at Oracle do want...

That's probably the most type-safe option. Do you care about backwards compatibility?

No new warnings even? That's a surprise. Thanks for making the fix, Dave