mirror of https://github.com/loot/loot-condition-interpreter.git synced 2026-07-27 14:16:09 -07:00

T

Oliver Hamlet 48ec04a95f Only cache some function results

Some functions evaluate more quickly without caching than with caching,
because they use data that is cached in a separate read-only cache
that's faster to check, and don't do anything complex with that data.

2018-10-06 13:38:55 +01:00

benches

Add benchmarks to help optimise result caching

2018-10-06 13:28:03 +01:00

src

Only cache some function results

2018-10-06 13:38:55 +01:00

.gitignore

Support reading file version from Windows executables

2018-10-05 19:52:51 +01:00

.travis.yml

Add Travis and AppVeyor config

2018-10-05 20:30:50 +01:00

appveyor.yml

Add Travis and AppVeyor config

2018-10-05 20:30:50 +01:00

Cargo.toml

Add benchmarks to help optimise result caching

2018-10-06 13:28:03 +01:00

LICENSE

Add MIT license

2018-10-05 20:21:14 +01:00

README.md

Update readme

2018-10-06 10:42:18 +01:00

README.md

loot-condition-interpreter

An experimental library for parsing and evaluating LOOT's metadata condition strings. Written in Rust. Very incomplete.

Goals:

Explore parsing conditions into an intermediate representation, then evaluating from that representation. LOOT's current parser evaluates conditions while parsing them, tightly coupling the two operations.
Explore more granular result caching. LOOT's current caching maps each condition string to its result, which can't re-use results in compound conditions.
Explore round trip serialisation from the intermediate representation.
Evaluate the cost/benefit of integrating into LOOT, replacing the existing code.

The tests need the testing-plugins and the LOOT API v0.13.8 Windows archives to be extracted and present in the repo root.