You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ To keep development of this project going, consider sponsoring. If you are
already a sponsor, thank you! ]
0.9.162
[ Please specify which version of babashka you're using. You can find this with babashka --version. The documentation on the master branch may be ahead of the most released version. ]
macOS 12.6 arm64
[ Please specify which platform you are using babashka on, so you can test a
new binary when the issue is resolved. ]
It looks like babashka 0.9.162 embeds core.async v1.5.648, which deprecates to-chan in favor of to-chan! and to-chan!!source code.
However, when I try to run some code using to-chan! with bb v0.9.162, I get this error:
* Map (on)to-chan!(!) core.async fns
These are recent replacements for their deprecated predecessors onto-chan & to-chan.
* Add note to changelog about #1370 fix
[ To keep development of this project going, consider sponsoring. If you are
already a sponsor, thank you! ]
0.9.162
[ Please specify which version of babashka you're using. You can find this with
babashka --version
. The documentation on the master branch may be ahead of the most released version. ]macOS 12.6 arm64
[ Please specify which platform you are using babashka on, so you can test a
new binary when the issue is resolved. ]
It looks like babashka 0.9.162 embeds core.async v1.5.648, which deprecates
to-chan
in favor ofto-chan!
andto-chan!!
source code.However, when I try to run some code using
to-chan!
with bb v0.9.162, I get this error:[ Please provide a short and to the point description of the problem ]
bb -e "(require '[clojure.core.async :refer [to-chan!]])"
[ Please provide a minimal working reproduction of the problem ]
When I run the same code with the tools.deps
clojure
command, it works.[ What is the behavior you expected to see? Please provide a minimal working example ]
The text was updated successfully, but these errors were encountered: