Mike Gerwitz
00ff660008
This begins demonstrating that the root will be utilized for identifier lookup and indexing, as it was originally for TAME and is currently for the linker. This was _not_ the original plan---the plan was to have identifiers indexed only at the package level, at least until we need a global lookup for something else---but that plan was upended by how externs are currently handled. So, for now, we need a global scope. (Externs are resolved by the linker in such a way that _any_ package that happens to be imported transitively may resolve the import. This is a global environment, which I had hoped to get rid of, and which will need to eventually go away (possibly along with externs) to support loading multiple programs into the graph simultaneously for cross-program analysis.) This commit renames the base state for `AirAggregate` to emphasize the fact, especially when observing it in the `AirStack`, and changes `AirAggregateCtx::lookup_lexical_or_missing` to resolve from the _bottom_ of the stack upward, rather than reverse, to prove that the system still operates correctly with this change in place. The reason for this direction change is to simplify lookup in the most general case of non-local identifiers, which are almost all of them in practice---they'll be immediately resolved at the root once they're indexed. This can be done because I determined that I will _not_ support shadowing; rationale for that will come later, but TAME is intended to be a language suitable for non-programmer audiences as well. Note that identifiers will be resolved lexically within templates in TAMER, unlike TAME, which means that the expansion context will _not_ be considered when checking for shadowing, so templates will still be able to compose without a problem so long as they do not shadow in their definition context. (I'll have to consider how that affects template-generating templates later on, but that's an ambiguous construction in TAME today anyway.) This _does not_ yet index anything at the root where it wasn't already being indexed explicitly. DEV-13162 |
||
|---|---|---|
| .. | ||
| benches | ||
| build-aux | ||
| src | ||
| tests | ||
| .gitignore | ||
| Cargo.lock | ||
| Cargo.toml | ||
| Makefile.am | ||
| README.md | ||
| autogen.sh | ||
| bootstrap | ||
| conf.sh.in | ||
| configure.ac | ||
| rustfmt.toml | ||
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.