|Enum Constant and Description|
Indicates that the value being looked for does not fit within the assumptions of the search.
Multiple literals, where the data referenced is a set of
Multiple references, where the data referenced is a sorted, unique set of ids.
A literal, where the value is encoded in the content id itself.
A typical singular reference where the content is known, typed, and not null.
An unknown (potentially changing) stream of ids as can be determined by executing the data referenced and can be treated like
Indicates missing data like the SQL null value.
A programmer's null which means "no value" unlike database null values for which you should use
|Modifier and Type||Method and Description|
Returns the enum constant of this type with the specified name.
Returns an array containing the constants of this enum type, in the order they are declared.
clone, compareTo, equals, finalize, getDeclaringClass, hashCode, name, ordinal, toString, valueOf
public static final Zomu.ZomuField ZERO
Zomu.UNKNOWN. The rest of the id can be anything, possibly random, possibly zeros; so while two zeros may both say the same thing, they may not be composed of the same bytes. You'll need to manage the comparison function depending on your context, but ignoring the bytes of zero ids would usually be safe, and compression schemes are officially licensed to cull that data, so if you put anything there, know that it's ephemeral.
public static final Zomu.ZomuField ONE_REFERENCE
public static final Zomu.ZomuField ONE_LITERAL
public static final Zomu.ZomuField MANY_REFERENCES
ONE_REFERENCEand they are all the same type as the
MANY_REFERENCESzomu id that identifies the set. The exception is where the type field is
Zomu.TypeField.ZOMU; in this case, the first two bytes of each id in the set are included because they may differ from each other.
public static final Zomu.ZomuField MANY_LITERALS
public static final Zomu.ZomuField POTENTIAL
MANY_ZOMU. This can be used with the common http url. The first thing a client should do with a
POTENTIALis to look up published memoizations.
POTENTIALgives the capability for lazy programming, where code may remain unexecuted or still in process until referenced, like Java futures and like Haskell thunks. But because of the nature of executable data, a client may choose to execute a potential again. Of course this is a relatively unsafe thing to do and it needs to be wrapped in a trust framework such as an app store with permissions systems etcetera. BaseParadigm being a polyglot system, the type on a
POTENTIALreference cannot be guaranteed in any way, and so the places where the type is unchecked.
public static final Zomu.ZomuField INAPPLICABLE
public static final Zomu.ZomuField UNKNOWN
UNKNOWN == UNKNOWNis
UNKNOWN != UNKNOWNis also
falsebecause neither value is known and so equality can not be established. Expressions involving an
public final Zomu zomu
public final byte code
public static Zomu.ZomuField values()
for (Zomu.ZomuField c : Zomu.ZomuField.values()) System.out.println(c);
public static Zomu.ZomuField valueOf(java.lang.String name)
name- the name of the enum constant to be returned.
java.lang.IllegalArgumentException- if this enum type has no constant with the specified name
java.lang.NullPointerException- if the argument is null