taatparya
Since Elixir 1.18.0, while under the left panel of the hexdocs Protocol is shown under Protocols category, the actual documentation page Protocol — Elixir v1.18.3, has the heading “Protocol behavior”. All other items in the category have headings with the protocol appended e.g. “Enumerable protocol”.
In the docs for till version 1.17, the heading is just “Protocol”. There is no change in the headings for other items in the protocols category.
Would like to understand better if this is not an oversight?
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Deploy Phoenix to your own VPS with PaaS ease: push-to-deploy, zero downtime, auto SSL, managed Postgres. 14-day free trial at potions.io
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #ai
- #phoenix_html
- #elixirconf-us
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Practical resources that improve the lives of professional developers.
Producing high quality Elixir screencasts since 2017.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 1- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
christhekeele
In 1.18.0, the
Protocolmodule was changed to be a behaviour, that gets automatically implemented in modules you create withdefprotocol.This change does not mean that modules that you implement with
defprotocolare also now behaviours. This is strictly an implementation detail ofProtocol, and does not affect modules created bydefprotocol, so the docs not changing for them is correct.The
ex_doclibrary that generates the documentation website uses introspection to automatically determine if it should add those behaviour subheaders to moduledocs. Now thatProtocolhappens to be a behaviour under the hood (but stdlib protocols still aren’t), that is reflected in the documentation. So this is not an oversight, just everything working well as intended.