Chris Rink

Thanks for the reply @ewjoachim. I'd already figured out the `Optional[int]` trick with timestamp which worked reasonably well, though I was still running into the later issue with the the...

I expanded on the previous commenter's view definition to handle a few extra things: * Some of the materialized views in my Redshift cluster take advantage of a custom `search_path`...

@ralokt many thanks for the initial report. Your investigation was invaluable for me trying to resolve this issue for our implementation. I wasn't able to get the signal solution you...

> Hi @chrisrink10, > > any chance you could review the `clojure.pprint` port to Basilisp, or perhaps suggest otherwise? I've just rebased to the latest main, and added a changelog...

@NoahTheDuke @ikappaki what do you consider the fundamental API for `clojure.pprint`? As I said above, I think the entire API is quite messy and confusing. I've never needed to use...

That makes sense. This is good context. I'm wondering if it's possible to both support the dynamic variables and use a context object and protocol (by capturing the values of...

What do you mean by "portable"? If we still respect the values of the dynamic vars if no context object is provided, then isn't that the same as JVM Clojure...

> By portable, I mean "Does this work without using reader conditionals?" `(seq [1 2 3])` is portable, `(java.io.StringWriter.)` is not. `clojure.pprint` has two arities, `[object]` and `[object writer]`. If...

Namespaces are cached by the Basilisp import mechanism (which is supported and facilitated by Python's own `importlib` machinery). Figuring out how to cache arbitrarily loaded code in a way that...

Clojure actually doesn't do this, so I'm skeptical it's the right move. It was originally going to be a component of supporting #851, but it felt a little scary to...