locmess 0.1.0

look at the mess that are your LOC
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34


[![Latest Version][s1]][l1] [![MIT][s2]][l2] [![Chat on Miaou][s3]][l3]

[s1]: https://img.shields.io/crates/v/locmess.svg
[l1]: https://crates.io/crates/locmess

[s2]: https://img.shields.io/badge/license-MIT-blue.svg
[l2]: LICENSE

[s3]: https://miaou.dystroy.org/static/shields/room.svg
[l3]: https://miaou.dystroy.org/3768?rust


Do you ever wonder about the distribution of LOC lengths in your source files ?

No ?

I do so I made **LocMess**.

![intro](doc/intro.png)

As an answer may bring another question, locmess tries to answer it too:

![over](doc/over.png)

and if you have yet another question, it's probably for `git blame`.

The source code of **LocMess**, which is totally not messy, may serve as a reasonnable basis for many kinds of transplatformy CLI applications. It's small so there's not much to remove to get to the pure boilerplate.