employer

tame

History

Mike Gerwitz 7b6d68af85 tamer: xir::parse::Transition: Generalize flat::Transition XIRF introduced the concept of `Transition` to help document code and provide mental synchronization points that make it easier to reason about the system. I decided to hoist this into XIR's parser itself, and have `parse_token` accept an owned state and require a new state to be returned, utilizing `Transition`. Together with the convenience methods introduced on `Transition` itself, this produces much clearer code, as is evidenced by tree::Stack (XIRT's parser). Passing an owned state is something that I had wanted to do originally, but I thought it'd lead to more concise code to use a mutable reference. Unfortunately, that concision lead to code that was much more difficult than necessary to understand, and ended up having a net negative benefit by leading to some more boilerplate for the nested types (granted, that could have been alleviated in other ways). This also opens up the possibility to do something that I wasn't able to before, which was continue to abstract away parser composition by stitching their state machines together. I don't know if this'll be done immediately, but because the actual parsing operations are now able to compose functionally without mutability getting the way, the previous state coupling issues with the parent parser go away. DEV-10863		2022-03-17 16:02:05 -04:00
..
benches	tamer: xir: Remove Text enum	2021-11-15 23:47:14 -05:00
build-aux	Copyright year update 2021	2021-07-22 15:00:15 -04:00
src	tamer: xir::parse::Transition: Generalize flat::Transition	2022-03-17 16:02:05 -04:00
.gitignore	TAMER: Initial commit	2019-11-18 14:05:47 -05:00
Cargo.lock	tamer: Update dependencies	2022-03-11 10:51:51 -05:00
Cargo.toml	tamer: Update dependencies	2022-03-11 10:51:51 -05:00
Makefile.am	tamer: cargo --frozen --offline	2021-12-02 11:49:51 -05:00
README.md	Copyright year update 2021	2021-07-22 15:00:15 -04:00
autogen.sh	Copyright year update 2021	2021-07-22 15:00:15 -04:00
bootstrap	tamer: cargo --frozen --offline	2021-12-02 11:49:51 -05:00
configure.ac	tamer: cargo --frozen --offline	2021-12-02 11:49:51 -05:00
rustfmt.toml	tamer/rustfmt (max_width): Set to 80	2019-11-27 09:15:15 -05:00

README.md

TAME in Rust (TAMER)

TAME was written to help tame the complexity of developing comparative insurance rating systems. This project aims to tame the complexity and performance issues of TAME itself. TAMER is therefore more tame than TAME.

TAME was originally written in XSLT. For more information about the project, see the parent README.md.

Building

To bootstrap from the source repository, run ./bootstrap.

To configure the build for your system, run ./configure. To build, run make. To run tests, run make check.

You may also invoke cargo directly, which make will do for you using options provided to configure.

Note that the default development build results in terrible runtime performance! See [#Build Flags][] below for instructions on how to generate a release binary.

Build Flags

The environment variable CARGO_BUILD_FLAGS can be used to provide additional arguments to cargo build when invoked via make. This can be provided optionally during configure and can be overridden when invoking make. For example:

# release build
$ ./configure && make CARGO_BUILD_FLAGS=--release
$ ./configure CARGO_BUILD_FLAGS=--release && make

# dev build
$ ./configure && make
$ ./configure CARGO_BUILD_FLAGS=--release && make CARGO_BUILD_FLAGS=

Hacking

This section contains advice for those developing TAMER.

Running Tests

Developers should be using test-driven development (TDD). make check will run all necessary tests.

Code Format

Rust provides rustfmt that can automatically format code for you. This project mandates its use and therefore eliminates personal preference in code style (for better or worse).

Formatting checks are run during make check and, on failure, will output the diff that would be applied if you ran make fmt (or make fix); this will run cargo fmt for you (and will use the binaries configured via configure).

Since developers should be doing test-driven development (TDD) and therefore should be running make check frequently, the hope is that frequent feedback on formatting issues will allow developers to quickly adjust their habits to avoid triggering formatting errors at all.

If you want to automatically fix formatting errors and then run tests:

$ make fmt check

Benchmarking

Benchmarks serve two purposes: external integration tests (which are subject to module visibility constraints) and actual benchmarking. To run benchmarks, invoke make bench.

Note that link-time optimizations (LTO) are performed on the binary for benchmarking so that its performance reflects release builds that will be used in production.

The configure script will automatically detect whether the test feature is unstable (as it was as of the time of writing) and, if so, will automatically fall back to invoking nightly (by running cargo +nightly bench).

If you do not have nightly, run you install it via rustup install nightly.