Lots of low hanging fruit e.g. invalid op codes, mapping errors to diagnostics, popping off an empty stack, removing unused code even.
Lots of low hanging fruit e.g. invalid op codes, mapping errors to diagnostics, popping off an empty stack, removing unused code even.
I was tasked to write tests for the core algorithm code. The code was written by the founder and it ALL looked like this. Zero comments.
I was tasked to write tests for the core algorithm code. The code was written by the founder and it ALL looked like this. Zero comments.
I'm building this to support parsing HTTP message templates. These will partial/non compliant messages but template references are restricted to individual message parts: method, url, header (key/value or the whole line, etc..)
I'm building this to support parsing HTTP message templates. These will partial/non compliant messages but template references are restricted to individual message parts: method, url, header (key/value or the whole line, etc..)
I usually last a month before it falls off and I pick back up a month after that.
I usually last a month before it falls off and I pick back up a month after that.
Other features planned
- Budget spans/ranges
- Expense buckets for those budget ranges e.g. food, gas
- Splitting a bill's payment (like a house payment) across multiple budget spans. Not making the payment but reserving the money
Other features planned
- Budget spans/ranges
- Expense buckets for those budget ranges e.g. food, gas
- Splitting a bill's payment (like a house payment) across multiple budget spans. Not making the payment but reserving the money
- High level dashboard (still WIP)
- Timeline view of events
- Calendar view with drag & drop transactions (planned, processing, complete), drag & drop bills, due dates/auto pays, rolling balance updates
Note: This is all mock/generated data
- High level dashboard (still WIP)
- Timeline view of events
- Calendar view with drag & drop transactions (planned, processing, complete), drag & drop bills, due dates/auto pays, rolling balance updates
Note: This is all mock/generated data
- `id` is a builtin function that accepts a value and returns the same value
` @_` is a placeholder for the REPL's last interpreted value
- `id` is a builtin function that accepts a value and returns the same value
` @_` is a placeholder for the REPL's last interpreted value
These tests much easier to write than the, macro driven, integration tests in place now.
What's really nice is that it makes experimenting in the system almost as fast as the REPL but you get tests in the end.
These tests much easier to write than the, macro driven, integration tests in place now.
What's really nice is that it makes experimenting in the system almost as fast as the REPL but you get tests in the end.