Sure, but if the protocol hasn't changed, does a new type need to be
generated? Maybe this is too much to ask, but I would imagine that the
compiler could inspect the current protocol of the same name and compare it
with the newly evaluated one, and then only generate a new type when
necessary
On Tuesday, June 19, 2012 5:53:41 PM UTC+1, David Nolen wrote:
>
>
> Looking forward to an Overtone API over WebAudio (
> http://chromium.googlecode.com/svn/trunk/samples/audio/index.html) :)
>
> David
>
This has been discussed briefly, but it would be a serious undertaking to
develop something
On Tue, Jun 19, 2012 at 12:14 PM, Sam Aaron wrote:
> It seems that guarding the protocol declarations inside of a defonce does
> the job nicely, although it is a big fugly. It's not too bad a trade-off
> though, because we rarely, if ever, want to change a protocol definition
> live. My main conc
It seems that guarding the protocol declarations inside of a defonce does the
job nicely, although it is a big fugly. It's not too bad a trade-off though,
because we rarely, if ever, want to change a protocol definition live. My main
concern is that it wasn't obvious what was breaking Overtone d
On Tue, Jun 19, 2012 at 10:49 AM, Phil Hagelberg wrote:
> Protocols necessarily make some unfortunate dynamicity trade-offs in the
> name of self-hosting. If you value interactive development over execution
> efficiency perhaps they are not the right choice.
>
> -Phil
>
Depending on what Clojure
Protocols necessarily make some unfortunate dynamicity trade-offs in the
name of self-hosting. If you value interactive development over execution
efficiency perhaps they are not the right choice.
-Phil
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
Hi,
I'm wondering if people might have advice on how to deal with the issue
of reloading protocol definitions. Currently in Overtone things break when
we reload some namespaces because once a defprotocol form is re-evaluated
the existing types that implement that protocol are no longer valid