Crate bare_proc

Source
Expand description

bare_proc provides a simple procedural macro that generates Rust types from BARE schema files. Generated types implicitly implement serde::Serialize and serde::Deserialize, as serde_bare is used to handle encoding and decoding. Please see serde_bare’s documentation for information on how the Rust data model maps to the BARE data model.

To use this macro, define a BARE schema file and populate it with type declarations.

For example:

// schema.bare
type PublicKey data[128]
type Time str # ISO 8601

type Department enum {
  ACCOUNTING
  ADMINISTRATION
  CUSTOMER_SERVICE
  DEVELOPMENT

  # Reserved for the CEO
  JSMITH = 99
}

type Address list<str>[4] # street, city, state, country

type Customer struct {
  name: str
  email: str
  address: Address
  orders: list<struct {
    orderId: i64
    quantity: i32
  }>
  metadata: map<str><data>
}

type Employee struct {
  name: str
  email: str
  address: Address
  department: Department
  hireDate: Time
  publicKey: optional<PublicKey>
  metadata: map<str><data>
}

type TerminatedEmployee void

type Person union {Customer | Employee | TerminatedEmployee}

Then, within a Rust source file:

use bare_proc::bare_schema;

bare_proc!("schema.bare");


let noah = Employee {
    name: "Noah",
    email: "noah@packetlost.dev",
    address: ["", "", "", ""],
    department: Department::ACCOUNTING,
    hireDate: Vec::<u8>::new(),
    publicKey: None,
    metadata: HashMap::new(),
};

§BARE => Rust Data Mapping

In most areas, the BARE data model maps cleanly to a Rust representation. Unless otherwise specified, the most obvious Rust data type is generated from a given BARE type. For example, a BARE option<type> is mapped to Rust’s Option<type>, BARE unions and enums are mapped to Rust enums. See below for opinions that this crate has around data types that do not map as cleanly or require additional explanation.

§Maps

BARE maps are interpreted as HashMap<K, V> in Rust. As of now, this is not configurable, but may be in the future.

§Variable Length Integers

The variable uint and int types are mapped to [serde_bare::UInt] and [serde_bare::Int] respectively. These types wrap u64 and i64 (the largest possible sized values stored in BARE variable length integers).

Arrays that have 32 or less elements are mapped directly as Rust arrays, while BARE arrays with more than 32 elements are converted into Vec<T>.

Macros§

bare_schema
bare_schema parses a BARE schema file and generates equivalent Rust code that is capable of being serialized to and deserialized from bytes using the BARE encoding format. The macro takes exactly one argument, a string that will be parsed as path pointing to a BARE schema file. The path is treated as relative to the file location of the macro’s use. For details on how the BARE data model maps to the Rust data model, see the Serialize derive macro’s documentation.