Clojurians Log v2

Ah fantastic. I've been playing around with similar ideas but haven't had time to do a full project. Very happy someone found the value here. @tony.kay Are you doing compile time analysis within forms bounded by the syntax that does actual runtime checks?

For example, the compile time check encounters a form that's a runtime check (e.g. a Malli validate call) and, assuming that check passes, can now assume what the current data shape can be?

There is no compile. I'm literally interpreting the code, and using generators and data flow analysis to look for possible problems. The checker runs within your env so it can use whatever specs and generators you've defined.

Okay I'll have to take a closer look. Sorry when I said "compile" what I meant was "compile time" which means you only have access to the source code state, not runtime state.

Congrats on finally releasing this :)

Yeah thanks. We talked about it a Loooooong time ago. At least now you can see what I was talking about 😄

This is very cool 😎

You might want to post this to the #rdf channel.

Hi @alexmiller I thought that if anyone was interested they could go into articles and repos created 😅 anyway I'll try to add more specific details here about > There is so much more we want to communicate and verify about our systems To allow systems to communicate about themselves, they need introspection support. Clojure offers different helpers depending the type of thing we want to query about: for vars & funs defined (meta) , for namespaces and ns mappings (ns-public, ns-map, ns-interns ...), for protocols (extenders, satisfies? ...), for defrecords (bases, supers), for multimethods (methods, get-method ) and for hierarchies (isa?, ancestors, descendants, parents). Each of these parts live separately and are not unified (data returned differs if var, function, namespace, protocol, record .. ) thus we can't answer basic system questions.... "Find all functions that take email as input" "GDPR audit: Which functions process email without encryption?" "Security review: What endpoints expose email without auth?" "Refactoring: Who still uses deprecated email-v1 spec?" "What breaks if I change user spec?" "Which endpoints expose PII without authentication?" "Find all functions storing user data without retention policies" https://github.com/semantic-namespace/contract lib addresses this gap by providing: - Unified RDF triple store - Cross-cutting semantic queries - Context-dependent relationships - Everything as queryable data Essentially builds a semantic layer on top of Clojure's var system, making the implicit relationships explicit and queryable as RDF triples. leaving here another example using endpoint as domain problem https://github.com/semantic-namespace/contract/blob/main/dev/src/semantic_namespace/endpoint_example.clj hope this new comment helps on clarifying the direction and purpose I'm trying to share

I am well-primed to be interested in this but even after seeing your talk and reading the announcement twice, I'm still unclear what problem you're trying to solve or what you are proposing to solve it. I generally understand and agree with the ideas outlined, just not sure what you're driving towards.