This change has now been pushed to master.
LiftRules.finder() has been removed since it offered (unsafe) duplicate
functionality.
cheers,
alex
On Mon, Jan 4, 2010 at 4:03 PM, Alex Boisvert alex.boisv...@gmail.comwrote:
Instead of:
LiftRules.getResourceAsStream(name: String):
On Sat, Jan 9, 2010 at 6:31 AM, Alex Boisvert alex.boisv...@gmail.comwrote:
This change has now been pushed to master.
LiftRules.finder() has been removed since it offered (unsafe) duplicate
functionality.
Excellent! Thanks!
cheers,
alex
On Mon, Jan 4, 2010 at 4:03 PM, Alex
On Mon, Jan 4, 2010 at 1:03 PM, Alex Boisvert alex.boisv...@gmail.comwrote:
Instead of:
LiftRules.getResourceAsStream(name: String): Box[InputStream]
I'd suggest:
LiftRules.doWithResource[T](name: String)(f: InputStream = T): Box[T].
Sounds good. Please open a ticket and make it happen.
Instead of:
LiftRules.getResourceAsStream(name: String): Box[InputStream]
I'd suggest:
LiftRules.doWithResource[T](name: String)(f: InputStream = T): Box[T].
And if you need laziness, you could use one of the usual suspects: lazy
val, unapplied function, FatLazy, etc.
alex
On Thu, Dec 31,
Folks,
I've changed LiftRules.getResourceAsStream and LiftRules.finder to return
Box[Applier[InputStream]] rather than Box[InputStream].
Applier has a single method, apply[T] which takes an InputStream = T and
insures the InputStream is closed.
This change is unlikely to impact much code out
StreamManager? (as in automatic resource management)
Stream
Don't like the above that much but nothing better comes to mind. Anyone?
Also should it be apply, or doWith for consistency with AnyVars?
-
David Pollakfeeder.of.the.be...@gmail.com wrote:
Folks,
