cljs-dev

dnolen 2023-11-29T15:28:12.197199Z

@quoll it’s probably not something to really prioritize, one problem is that anything that cljs.core requires people might use directly.

quoll 2023-11-29T15:33:41.108809Z

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) 😊

dnolen 2023-11-29T16:07:59.619029Z

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.

quoll 2023-11-29T18:17:51.304709Z

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 🙂

quoll 2023-11-29T18:18:49.244729Z

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

👍 1