my nemesis

"we're a dynamic language, you can redefine anything" /me tries to redefine one thing "not like that"

I've tried monkeypatching clojure.core/alias, but it doesn't work, presumably because of AOT or direct linking or something.

It's not too hard to build your own Clojure, mvn install it locally as 1.99.99 and have such tweaks over there I have for the last couple years without major headaches. Given clj's stable pace, keeping up with upstream has been a breeze!

how do you benefit from that on a team @U45T93RA6?

I keep it to myself, it's in my user profile

can't say I haven't considered it, and I've done my own build when tinkering with using it on android because I had to.

I'm starting to think of going the java agent route and integrating it with launchpad https://github.com/lambdaisland/launchpad

@U0509NKGK you could totally push your own build to clojars or elsewhere and use that as a dev dependency too, but rebuilding for every release seems tedious.

It also just feels iffy... having to answer the question "is that a bug or is it just some weirdness with our custom build?"

yeah

channeling my rightous rage towards Alex 😛 https://ask.clojure.org/index.php/12235/can-alias-already-exists-in-namespace-be-fixed

aw i can only upvote it once

Got a WONTFIX from Fogus :( https://ask.clojure.org/index.php/12235/can-alias-already-exists-in-namespace-be-fixed?show=12250#a12250

This might have to be the point where I angrily stomp off and release a fork 😝

(jk)

"it's a mischaracterization that the staircase is broken, yes people fall off routinely, but that's because it follows the broken staircase school of architecture. We can however consider putting a sign next to it."

awww

could in theory write an nrepl middleware that catches and and calls ns-unalias?

yeah, that could be an option, catch-unalias-eval-again