Meeseeks (library)
Tracked files: 88 (nodes)
Compile dependencies: 67 (edges)
Structs dependencies: 102 (edges)
Runtime dependencies: 77 (edges)
mischov
1
belaustegui
I didn’t know about this. It looks like a great improvement and will reduce both our recompilations and their time.
Is there any place where I can get more information on this matter? It is really interesting 
1
christhekeele
On a prod-dependency-less library (no phoenix/ecto/nerves), based on exenv install master @ commit ebe33f1f:
$ mix xref graph --format stats
Generated mnemonix app
Tracked files: 34 (nodes)
Compile dependencies: 83 (edges)
Structs dependencies: 11 (edges)
Runtime dependencies: 64 (edges)
deps:
[
{:benchfella, "~> 0.3", only: [:dev, :test]},
{:cortex, "~> 0.4", only: [:dev, :test]},
{:credo, "~> 0.6", only: [:dev, :test]},
{:dialyzex, "~> 1.0", only: [:dev, :test]},
{:excoveralls, "~> 0.6", only: [:dev, :test]},
{:ex_doc, "~> 0.15", only: [:dev, :test]},
{:inch_ex, "~> 0.5", only: [:dev, :test]},
{:elastix, ">= 0.4.0", only: [:dev, :test]},
{:memcachex, ">= 0.0.0", only: [:dev, :test]},
{:redix, ">= 0.0.0", only: [:dev, :test]},
{:plug, ">= 0.0.0", only: [:dev, :test]},
]
1
OvermindDL1
It is limited on purpose, it is an example of what ‘should’ be done, but I very much on purpose left it incomplete. ^.^
Pretty trivial to add, just not done as it was not needed to perform my example API.
I specifically don’t handle the case of it being called straight out to try to get people not to use it, it is just showing the API and how it should work. ^.^
Yep yep, showing how it works, those are the tests.
I started that work but stopped it so as to help minimize the use of the library.
Ditto, started that work but stopped it as well.
I ‘could’, but this library works by overriding def itself, which I consider very poor form, and hence is also why I think this style belongs in Elixir itself, not as a library. It could be entirely functional, just I find overriding def to be very very poor form… ^.^;
Whoooo! Already using this. ^.^
Now if only the formatter would not destroy my nicely formatted and readable lists of numbers in a very specific format as well as my nicely format binary matching/building that practically matches the spec (though neither look like anything except a mess after mix format is run… >.<). ^.^;
1
mjadczak
It would be nice to have some sort of @verbatim / @endverbatim to keep certain code sections as-is with mix format, has this been discussed already?
2
LostKobrakai
Here’s the relevant github issue: Formatting of large binary pattern matches · Issue #7152 · elixir-lang/elixir · GitHub
4
axelson
Scenic Core Team
Adding stats for a Phoenix (1.2) project that’s been in production for more than a year:
Tracked files: 179 (nodes)
Compile dependencies: 271 (edges)
Structs dependencies: 69 (edges)
Runtime dependencies: 448 (edges)
The number of compile and runtime dependencies seem to be much higher than the average. Should probably do some re-architecture to bring that down.
2