Alternative names to defmodulep (split thread)

I believe some of that work was included in the 1.11 release - elixir/CHANGELOG.md at v1.11 · elixir-lang/elixir · GitHub

so next question: is there any plan to merge boundary(or modified version of it) into core Elixir? That would be nice

As mentioned in the proposal discussion, we favored option A and Boundary provides a more complete implementation - so I would advise to use that. We have no plans to introduce defmodulep in core. You can see the proposal discussion for my rationale.

I know is archived, sorry to have mislead you about my intentions in my question. I don’t want to use it directly, but instead my question intention was when could we expect it in Elixir itself.

I though the repo for defmodulep was a playground for this proposal by Jose, but I noticed now that unfortunately it seems the preference goes to option A.

Any idea when Option A will be available in Elixir core?

I am not planning in developing a new library at all, and I already know about Boundary, but I was really expecting to have private modules in Elixir. I would prefer this to be built-in in the language then enforced by a dependency.

I don’t think defmodulep was ever on a track to be generally available/used, it was created more as a proof of concept. And now that the repository is archived it will no longer be developed (although of course if it Apache v2.0 so you can fork and maintain it if you want).

But I think that Boundary - enforcing boundaries in Elixir projects is a more promising alternative so I’d recommend you take a look at that instead or develop a new library.

Any idea when defmodulep will be available?

I just found defmodulep… Seems to me like the playground for the idea, or its the official implementation?

Since erlang requires a declaration of which functions are exported, yeah, I think the idea was considered. I have mixed feeling on the result, but I don’t question its consideration. In any case this is a majorly backwards incompatible change that would require a very strong argument to support it.

I haven’t read through all the threads on this topic but has the community thought about going the route Rust took, where every function is private by default? To make something public you have to declare it public like:

pub def this_is_my_public_facing_api(), do: # do something great

This way we don’t have to worry about private modules or whatever.

I think the bikeshed should be painted green, for what its worth