llogiq
llogiq
For code coverage, the score is usually posted somewhere to put on a badge or something, but I can see allowing for a threshold that needs to be reached to...
I just talked to a former colleague who works in statistical data processing. For interop reasons they work with binary files containing the data as fixed-width rows of little-endian 16-bit...
Let's try that again: @all-contributors please add @fretz12 for awesome ideas.
I guess we wanted to split the date/time types from the formatting. With that, the format would produce a string node.
On a cursory glance, this looks good. I'll have to test run it, and we'll need to rebase before merging though. I'll let you know when I've done the test...
While we're at it, we should probably look into #28 regarding escaping (at least for Postgres).
I think we should be able to do this, at the expense of requiring a global `#![flamer]` annotation. Then we'd just keep a stack of modules, etc. and prepend that...
I believe this should be fine by #6. Needs a test case though. Edit: No it isn't.
So you'd like a `#[flame(pub)]` annotation that only instruments public items?
Huh? That one is new. I think it may have to do with some recent changes in the AST logic.