Dan Rose

> I initially overlooked it! You had me questioning my sanity there!

I'm unclear at this point the status of `predicate_property/2` vis-à-vis ISO/IEC 13211-2. Is it intended to specify the standard predicate? Or is it a built-in implementation-specific predicate that happens to...

Relevant discussion in #2933. Reading between the lines, it seems the property of being "public" in the ISO sense might not be as useful as it seemed at first blush....

I think this may be a downstream issue of https://github.com/microsoft/TypeScript/issues/58020 If I replace `get foo(): X` with `readonly foo: X` in all my type expressions, I don't seem to get...

It seems there's a fairly big terminology rift between ISO/IEC 13211-1 and SICStus in what they mean by "public". I think ISO "accessible" = SICStus "public". > ### 4.11.2 Basic...

The primary use of `public` is for debugging and introspecting. Even just having some rough idea of what a predicate looks like is good enough, even if it’s not a...

> please do include ellipses when quoting the standard :+1: Trying to understand Prolog by reading the ISO spec is probably going to be part of my supervillain origin story!...

> > Trying to understand Prolog by reading the ISO spec is probably going to be part of my supervillain origin story! > > Did you start with the scope?...

@triska > Regarding phrasings such as "a flag that allows us to break with the spec", I note for example: > ... > A conforming implementation can in many ways...

> > ... [spec continued] ... > > You deleted the reference to [SC22](https://www.iso.org/committee/45202.html) where you get the most up to date ~status~ stage. In fact, I received the information...