package lambdabuffers.compiler

Get desktop application:
View/edit binary Protocol Buffers messages

Compiler Error

Used in: Output

• repeated ProtoParseError proto_parse_errors = 1

  Errors occurred during proto parsing.

• repeated NamingError naming_errors = 2

  Errors occurred during naming checking.

• repeated KindCheckError kind_check_errors = 4

  Errors occurred during kind checking.

• repeated TyClassCheckError ty_class_check_errors = 5

  Errors occurred during type class checking.

• repeated InternalError internal_errors = 6

  Errors internal to the compiler implementation.

Compiler Input Compiler Input is a fully self contained list of modules, the entire compilation closure needed by the Compiler to perform its task.

• repeated Module modules = 1

  Modules to compile. Duplicate modules MUST be reported with `ProtoParseError.MultipleModuleError`.

Errors internal to the implementation.

Used in: Error

• string msg = 1

  Error message.

• optional SourceInfo source_info = 2

  Source information if meaningful.

Kind checking errors.

Used in: Error

• oneof kind_check_error

  One of the errors occurred during kind checking.

  • KindCheckError.UnboundTyRefError unbound_ty_ref_error = 1

  • KindCheckError.UnboundTyVarError unbound_ty_var_error = 2

  • KindCheckError.UnificationError unification_error = 3

  • KindCheckError.CyclicKindError cyclic_kind_error = 4

  • KindCheckError.InconsistentTypeError inconsistent_type_error = 5

A cyclic kind was encountered. Infinite kinds like this are not acceptable, and we do not support them. We could not construct infinite kind in ty_def. As the implementation currently stands such an error is (most likely) not representable - therefore not reachable. Such an error would usually occur for a term like: λa. a a - in which case the inference would try to unify two kinds of the form: m and m -> n - because m appears in both terms - the cyclic unification error would be thrown. In the case of LambdaBuffers - such an error is not (currently) achievable as the kind of the variable is given by the context - (i.e. λa : m . a a, where m is a kind) therefore the unification would fail with Unification Error. Nevertheless - future features might require it.

Used in: KindCheckError

• optional TyDef ty_def = 1

• optional ModuleName module_name = 2

The actual_kind differs from the expected_kind.

Used in: KindCheckError

• optional ModuleName module_name = 1

• optional TyDef ty_def = 2

• optional Kind actual_kind = 3

• optional Kind expected_kind = 4

Unbound type reference ty_ref detected in term ty_def.

Used in: KindCheckError

• optional ModuleName module_name = 1

• optional TyDef ty_def = 2

• optional TyRef ty_ref = 3

Unbound variable ty_var detected in term ty_def.

Used in: KindCheckError

• optional ModuleName module_name = 1

• optional TyDef ty_def = 2

• optional TyVar ty_var = 3

In ty_def an error has occurred when trying to unify kind ty_kind_lhs with ty_kind_rhs. FIXME(cstml): Add source of constraint to the error such that user can see where the constraint was generated - therefore where the error precisely is.

Used in: KindCheckError

• optional ModuleName module_name = 1

• optional TyDef ty_def = 2

• optional Kind ty_kind_lhs = 3

• optional Kind ty_kind_rhs = 4

Naming error message

Used in: Error

• oneof naming_error

  One of naming errors.

  • ModuleNamePart module_name_err = 1

  • TyName ty_name_err = 2

  • VarName var_name_err = 3

  • ConstrName constr_name_err = 4

  • FieldName field_name_err = 5

  • ClassName class_name_err = 6

Output of the Compiler.

• oneof output

  • Error error = 1

  • Result result = 2

All errors that occur because of Google Protocol Buffer's inability to enforce certain invariants. Some of invariance: - using Proto `map` restricts users to `string` keys which impacts API documentation, which is why `repeated` fields are used throughout, - using Proto 'oneof' means users have to check if such a field is set or report an error otherwise.

Used in: Error

• oneof proto_parse_error

  • ProtoParseError.MultipleModuleError multiple_module_error = 1

  • ProtoParseError.MultipleTyDefError multiple_tydef_error = 2

  • ProtoParseError.MultipleClassDefError multiple_classdef_error = 3

  • ProtoParseError.MultipleTyArgError multiple_tyarg_error = 4

  • ProtoParseError.MultipleConstructorError multiple_constructor_error = 5

  • ProtoParseError.MultipleFieldError multiple_field_error = 6

  • ProtoParseError.MultipleImportError multiple_import_error = 7

  • ProtoParseError.OneOfNotSetError one_of_not_set_error = 8

  • ProtoParseError.UnknownEnumError unknown_enum_error = 9

Multiple ClassDefs with the same ClassName were found in ModuleName.

Used in: ProtoParseError

• optional ModuleName module_name = 1

  Module in which the error was found.

• repeated ClassDef class_defs = 2

  Conflicting class definitions.

Multiple Sum Constructors with the same ConstrName were found in ModuleName.TyDef.

Used in: ProtoParseError

• optional ModuleName module_name = 1

  Module in which the error was found.

• optional TyDef ty_def = 2

  Type definition in which the error was found.

• repeated Sum.Constructor constructors = 3

  Conflicting constructors.

Multiple Record Fields with the same FieldName were found in ModuleName.TyDef.

Used in: ProtoParseError

• optional ModuleName module_name = 1

  Module in which the error was found.

• optional TyDef ty_def = 2

  Type definition in which the error was found.

• repeated Record.Field fields = 3

  Conflicting record fields.

Used in: ProtoParseError

• optional ModuleName module_name = 1

  Module in which the error was found.

• repeated ModuleName imports = 2

  Conflicting module imports.

Multiple Modules with the same ModuleName were found.

Used in: ProtoParseError

• repeated Module modules = 2

  Conflicting type definitions.

Multiple TyArgs with the same ArgName were found in ModuleName.TyDef.

Used in: ProtoParseError

• optional ModuleName module_name = 1

  Module in which the error was found.

• optional TyDef ty_def = 2

  Type definition in which the error was found.

• repeated TyArg ty_args = 3

  Conflicting type abstraction arguments.

Multiple TyDefs with the same TyName were found in ModuleName.

Used in: ProtoParseError

• optional ModuleName module_name = 1

  Module in which the error was found.

• repeated TyDef ty_defs = 2

  Conflicting type definitions.

Proto `oneof` field is not set.

Used in: ProtoParseError

• string message_name = 1

  Proto message name in which the `oneof` field is not set.

• string field_name = 2

  The `oneof` field that is not set.

Proto `enum` field is unknown.

Used in: ProtoParseError

• string enum_name = 1

  Proto `enum` name.

• string got_tag = 2

  The unknown tag for the `enum`.

Compiler Result ~ a successful Compilation Output.

Used in: Output

(message has no fields)

Type class checking errors.

Used in: Error

• oneof tyclass_check_error

  One of the errors occurred during type class checking.

  • TyClassCheckError.UnboundClassRefError unbound_class_ref_err = 1

  • TyClassCheckError.SuperclassCycleError superclass_cycle_err = 2

  • TyClassCheckError.ImportNotFoundError import_not_found_err = 3

  • TyClassCheckError.DeriveOpaqueError derive_opaque_err = 4

  • TyClassCheckError.MissingRuleError missing_rule_err = 5

  • TyClassCheckError.OverlappingRulesError overlapping_rules_err = 6

In `module_name` it wasn't possible to solve `constraint` because a `sub_constraint` has been derived on an `Opaque` type. `Opaque` type can only have an `InstanceClause` declared for them.

Used in: TyClassCheckError

• optional ModuleName module_name = 1

• optional Constraint constraint = 2

• optional Constraint sub_constraint = 3

Import `missing` wasn't found in `module_name`

Used in: TyClassCheckError

• optional ModuleName module_name = 1

• optional ModuleName missing = 2

In `module_name` while trying to solve `constraint` it wasn't possible to find a rule (`Derive` or `InstanceClause`) for `sub_constraint`.

Used in: TyClassCheckError

• optional ModuleName module_name = 1

• optional Constraint constraint = 2

• optional Constraint sub_constraint = 3

In `module_name` while trying to solve `constraint` `overlaps` (`Derive` or `InstanceClause`) were found that could be used to solve the `sub_constraint`.

Used in: TyClassCheckError

• optional ModuleName module_name = 1

• optional Constraint constraint = 2

• optional Constraint sub_constraint = 3

• repeated OverlappingRulesError.QHead overlaps = 4

NOTE(bladyjoker): This should rather be oneof `Derive` and `InstanceClause`.

Used in: OverlappingRulesError

• optional ModuleName module_name = 1

• optional Constraint head = 2

Superclass cycle `cycled_class_refs` was detected when checking a class definition for `class_name` in module `module_name`.

Used in: TyClassCheckError

• optional ModuleName module_name = 1

• optional ClassName class_name = 2

• repeated TyClassRef cycled_class_refs = 3

Unbound `class_ref` detected in `module_name`.

Used in: TyClassCheckError

• optional ModuleName module_name = 1

• optional TyClassRef class_ref = 2