Either would be the purely stdlib way to go, and Naftoli is right
that it would be a lot more verbose. I would argue that the
difference isn't *so* substantial if you sprinkle in a type alias and
some implicit conversions (so that you can map/flatMap/filter over
something of type
Back when I was the only Lift committer (okay, maybe SteveJ had commit
rights back then... I don't remember) and I was working on the first
Lift-based app, I was experiencing a nasty issue. This was summer of 2007.
This was circa Scala 2.4 and before Either was in the language. One of the
It sometimes seems to me that people are view-ing Option as an
absolute term - a complete Maybe monad that everyone should obey.
Yeah, that's pretty much it. :-) Saying that you have a replacement
Option with totally different instances is like telling me that you
have a new definition for a
I'm sure this has been discussed before, but I'm curious as to the
rationale for the Box ADT. I'm most distressed by the fact that it
seems to be masquerading as a drop-in Option replacement, and yet the
mathematical properties of the ADT are widely divergent. What's more,
the API is very, very
We can make fixes to the 1.0.x branch for you, but I am reluctant to make
changes to the 1.0 version.
Very understandable. We'll just bump up to the 1.0.2 release. That
jump has been on the back burner for a while, so it's good to get an
excuse to push it through. :-)
You might look into
/Unlisten logic).
On Tue, Jan 12, 2010 at 10:25 AM, Daniel Spiewak djspie...@gmail.comwrote:
We're already using the Comet support within Lift quite extensively
across the board. There are very, very few pages in our application
which do not have a CometActor embedded in them at some level
I'm looking to implement a user presence feature (think: Facebook or
Gmail chat) in a Lift 1.0 application. Ideally, I would like to avoid
adding extraneous connections. Is it possible to hook into the Lift
Comet heartbeat which is already in use across our system? I've
looked at the source for
We're already using the Comet support within Lift quite extensively
across the board. There are very, very few pages in our application
which do not have a CometActor embedded in them at some level of
nesting.
Daniel
On Jan 12, 12:08 pm, Naftoli Gugenheim naftoli...@gmail.com wrote:
You are
, Jan 12, 2010 at 10:25 AM, Daniel Spiewak djspie...@gmail.comwrote:
We're already using the Comet support within Lift quite extensively
across the board. There are very, very few pages in our application
which do not have a CometActor embedded in them at some level of
nesting.
Daniel
