--
You received this message because you are subscribed to the Google Groups "elixir-lang-core" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elixir-lang-core+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/CA%2BbCVstDKAZZVPVMqgpqNLN2TuxK75S5_0kqHTh07vdeA3m%3DsQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
We don't have conversion functions in Kernel and they are not even auto imported in Erlang, so we would need strong reasons to import them in Elixir. If discovery is a reason for adding functions to Kernel, then we can end-up with a bloated Kernel quite quickly.On Fri, Dec 22, 2017 at 2:13 PM, Norbert Melzer <timm...@gmail.com> wrote:
`:erlang.binary_to_term/1` and `:erlang.term_to_binary/1` are used in the erlang world quite often to serialize data for network, disk, or ports in an efficient manner.In the elixir ecosystem they seem to be quite unknown and serialisation does often happen to and from JSON.By including, documenting, and even autoinlining from Kernel (such that they get auto-imported) I think we could massively increase the awareness of the elixir community about these functions.Bye,Norbert
--
You received this message because you are subscribed to the Google Groups "elixir-lang-core" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elixir-lang-co...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/CA%2BbCVstDKAZZVPVMqgpqNLN2TuxK75S5_0kqHTh07vdeA3m%3DsQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "elixir-lang-core" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elixir-lang-co...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/CAGnRm4KMaYJ-jWARdLCG530-949kPYv14NQ3-9UprUQ84HN9JA%40mail.gmail.com.