I’m suggesting this as something that cljs.core could use, instead of the goog libs. (And yes… whatever cljs.core uses is absolutely fair game for me. That’s actually why I started using the goog libs in the first place) 😊

right just pointing out that you can’t elide the requires. Otherwise I don’t see a serious problem with it other than it will probably make cljs.core a little bit bigger advanced compiled.

That makes sense, given that it would be implemented in cljs rather than js. That said, cljs.core does not use a lot of classes from goog, so it may not be much. As an aside, I’ve run into a bug in goog.Uri so this could be an opportunity to fix things like that 🙂

The bug is that empty fragments are dropped entirely, which violates the RFC (and causes problems in many Semantic Web applications)