Is there any documentation about what hydrated vs ...
# development
h
Is there any documentation about what hydrated vs unhydrated means? I’ve been curious this whole time
a
Unhydrated: "Pretty much what you read from the file" Hydrated: "Anything that looks like a reference to something else (another target, a file on disk, ...) is a pointer to, or somehow references, that actual thing" So in options parsing (where I don't think we use this terminology) an unhydrated option may be a "FromFile(/some/file)" and a hydrated option may be "ignore_errors=True" after that file is read
w
the general "hydrated" vs "unhydrated" concept is a spectrum from "expensive to compute" to "cheap to compute", respectively
in the BUILD file parsing context in particular, https://github.com/pantsbuild/pants/issues/4535 has more info in its description
👍 1
i'm not attached to the terminology... as 4535 mentions, these APIs are all temporary, and you almost certainly don't want to include anything about hydration in the name of your most commonly used object type (ie, Target)
a
i use "hydrated" honestly way too often for lots of things it's a nice word
h
So is every “thing” either hydrated or unhydrated? Or the idea is certain things start unhydrated, and then become hydrated?
a
the latter
👍 1
and when hydrated they have things like pointers to dependencies that are these big shared memory trees so also implies like “hydrated” meaning linked together in some way