The most convenient structures for financial and economic unitemporal and bitemporal data, period.
Stars
4
Forks
0
Watchers
4
Open Issues
5
Overall repository health assessment
No package.json found
This might not be a Node.js project
11
commits
Fixed test. Comparison-by-start performance is x12-20 slower than int64. My rationale is probably wrong - storing period info (freq, ength) per table/series is ok. Period usage should be limited to storage/DTOs
5f6eedfView on GitHubRemove 'inline', fix missed non-tick flag in the constructor
b393b3fView on GitHubRadically simplify the layout. AKA remove premature optimization and brainfuck that DateTime operations could be slow. All I need is total ordering and int difference. This all happens inside L1 with int64/bitwise ops.
2743d39View on GitHubFinalized bit layout, added readme and picture. Still no tests, assume bugs and stupid errors are here.
2095407View on GitHub