package edgir.ref

Mouse Melon logoGet desktop application:
View/edit binary Protocol Buffers messages

message LibraryPath

ref.proto:78

* This is a path to an element within a library from the root of a library. To be used as a way to reference such elements.

Used in: elem.BlockLibrary, elem.HierarchyBlock, elem.Link, elem.LinkArray, elem.LinkLike, elem.Port, elem.PortArray, elem.PortLike, edgrpc.hdl.BackendRequest, edgrpc.hdl.GeneratorRequest, edgrpc.hdl.IndexResponse, edgrpc.hdl.LibraryRequest, edgrpc.hdl.RefinementRequest, edgrpc.hdl.Refinements.Subclass, edgrpc.hdl.Refinements.Value.ClassParamPath

message LocalPath

ref.proto:70

* This is a path from a local context to some other local context. To be used as a reference.

Used in: elem.Generator, elem.Parameter, expr.AssignExpr, expr.MapExtractExpr, expr.ValueExpr, edgrpc.compiler.CompilerResult.Connection, edgrpc.compiler.CompilerResult.Value, edgrpc.compiler.ErrorRecord, edgrpc.hdl.BackendResponse.Result, edgrpc.hdl.ExprValue, edgrpc.hdl.Refinements.Subclass, edgrpc.hdl.Refinements.Value, edgrpc.hdl.Refinements.Value.ClassParamPath

message LocalStep

ref.proto:43

* This is an actual step you take within the local environment. The directions encode the type of thing we are referencing, but to the user all of these look just like local variables

Used in: LibraryPath, LocalPath

enum Reserved

ref.proto:21

* These are reserved terms that we'll end up using in various places. I'd rather have these in the block/link/bridges where they're going to exist, but that's not possible without polymorphism protibuf doesn't have

Used in: LocalStep