On 12/16/20 2:08 AM, Markus Armbruster wrote:
We all have our phobias. I find "isinstance(x,
extremely_common_stdlib_type)" to be extremely fragile and likely to
frustrate.
You're applying programming-in-the-large reasoning to a
programming-in-the-small case.
"Surely, they won't use my proof
John Snow writes:
> On 11/16/20 5:12 AM, Markus Armbruster wrote:
>> John Snow writes:
>>
>>> This replaces _make_tree with Annotated(). By creating it as a generic
>>> container, we can more accurately describe the exact nature of this
>>> particular value. i.e., each Annotated object is actua
On 11/16/20 5:12 AM, Markus Armbruster wrote:
John Snow writes:
This replaces _make_tree with Annotated(). By creating it as a generic
container, we can more accurately describe the exact nature of this
particular value. i.e., each Annotated object is actually an
Annotated, describing its cont
John Snow writes:
> This replaces _make_tree with Annotated(). By creating it as a generic
> container, we can more accurately describe the exact nature of this
> particular value. i.e., each Annotated object is actually an
> Annotated, describing its contained value.
>
> This adds stricter typin
On Mon, Oct 26, 2020 at 03:42:49PM -0400, John Snow wrote:
> This replaces _make_tree with Annotated(). By creating it as a generic
> container, we can more accurately describe the exact nature of this
> particular value. i.e., each Annotated object is actually an
> Annotated, describing its contai
This replaces _make_tree with Annotated(). By creating it as a generic
container, we can more accurately describe the exact nature of this
particular value. i.e., each Annotated object is actually an
Annotated, describing its contained value.
This adds stricter typing to Annotated nodes and extra
