Kyle Hayes

The real problem is that each segment in a path is a pair of port/node. The port part is relatively limited to smaller numbers (

This should solve #443.

I've been trying to figure out how to do this. The problem is that we have just a number. You cannot tell whether that number is supposed to be a...

Hmm, I think I am overthinking this. I just need to parse the path in pairs. port/link is one such pair. The second part does not need to be less...

Changing this to an enhancement. This needs to happen soon.

Try a path of "0,0". IIRC, that is correct for those PLCs. I do not have one to test on so I am not sure.

It would be difficult to make this work when setting it lower at runtime. It could orphan some requests. Setting it higher could possibly work but is probably not a...

BTW, this is exposed in the wiki section on type-specific attributes. This is a bit of a mess, isn't it?

C has CHAR_BIT so perhaps something like that? Perhaps a const `std.?cpu?.smallest_addressable_unit_bits`? I **definitely** like the idea of being able to determine this in a well supported way, but I...

I like the symmetry of the "bag of bits" data type with the i* and u* types. I.e. i1, u1, bits1; i2, u2, bits2... i16, u16, bits16... Going off on...