I think Rich would agree with you

by “argued” do you mean just sitting around talking in a chat room or on a ticket?

I'm sure I've written about it in a mailing list years ago, but not ticket that I remember of as I never got feedback about it

I would be happy to make a ticket + patch making those unboxing hints invalid so that it doesn't trip people over (myself included, as the above clearly shows how I forgot about it :)) but need to know there is interest in that before spending time on it

ATM all I know is that I believe it to be an invalid type hint usage based on my understanding of the compiler /language semantics but I have no idea of my interpretation is correct

don't read too much into that 'argued about it' above btw, I just meant it as 'ah, how stupid I am, I've told people in the past not to make this mistake and now I've made it myself'

gotcha

I’m having trouble with the latest patch

@bronsa ^^

trying it on some public projects I’m seeing errors like "Unable to resolve symbol: inst_23951 in this context"

ex: https://github.com/nervous-systems/eulalie, https://github.com/metabase/metabase (lein expectations there)

😞

"it's a simple lexical transformation" I said

I'll see if I can take another look at this this evening

thanks

I think working on classloader issues was less painful than this

I’m going to move forward testing the current state w/o the patch for now

yeah no worries

thanks for all the testing

np

@alexmiller hmm, I'm getting that exception w/o my patch applied

and it's manifesting itself on a nested try in a go

I think it might be an issue with the try catch changes that went in rather than with my patch

(defn foo [x]
  (async/go
    (try
      (try
        (async/<! x)
        (catch clojure.lang.ExceptionInfo e
          (async/<! x)
          (throw e)))
      (catch Exception e e))))

smallest repro ^

failing on current master

\cc @hiredman

(defn foo []
  (async/go
    (try
      (catch clojure.lang.ExceptionInfo e
        (async/<! 1)
        (throw e)))))

appears to be the same error from that, and it seems to go away if I comment out the throw

yeah

try replacing (throw e) with just e

think that might be the smallest repro we can get

yep

(async/go
  (try
    (catch Exception e
      (async/<! 1)
      e)))

core.async: fix 5 bugs, create 2 more

compilers are hard man

:)

@bronsa apologies for misattributing the error :)

ah no worries

i get a kick out of debugging those things regardless of whose patch introduced them ;)

I haven't found a quick fix for this

I'll take a look at it later in case you can't find a fix

I think I got it (patch forth coming)

when I fixed the reflection on printStackTrace issue, I used with-meta instead of vary-meta, and it turns out there was some metadata there that the macro uses to figure out what to save between state machine invocations

I reopened the issue and added a new patch http://dev.clojure.org/jira/browse/ASYNC-169

nice