stevensonmt

stevensonmt

When you use the :digraph module and want to get a list of all edges, one would expect to see a list of vertex pairs, ideally with the “emanate from” / “incident to” order consistent. So something like [{:a, :b}, {:b, :c}, {:c, :b}] for a graph with vertices [:a, :b, :c] where :a has an edge incident to :b and :b and :c have a bidirectional edge. Instead you might see something inscrutable like [[:"$e" | 0], [:"$e" | 1], [:"$e" | 2]]. How are you supposed to interpret that list?

Showing Posts 1 to 8

al2o3cr

al2o3cr

Definitely an odd design choice - you could get something closer to what you’re looking for by mapping :digraph.edge over the output of :digraph.edges, but that’s a lot of round-trips to ETS to get what could have been one call to :ets.select :thinking:

https://github.com/erlang/otp/blob/e78684732252a5b2b33de90adaf8f7ff80eb5a3c/lib/stdlib/src/digraph.erl#L307-L334

bjorng

bjorng

Erlang Core Team

Alternatively, you could specify you our own edge names when creating the edges. As long as there is only a single edge in each direction between each pair of vertices, the following should work:

:digraph.add_edge(g, {from, to}, from, to, [])
stevensonmt

stevensonmt OP

So that’s brilliant. I’m curious why that’s not the default behavior of add_edge/3 though? Implicitly naming an edge with {from, to} has to be more intuitive than whatever [:"$e" | N] is meant to convey.

I also think it’s difficult to understand that this is possible from the docs for add_edge/5 because the edge() type is not documented. It’s also confusing to have edge “names” differ from edge “labels” and not document the “names” anywhere.

jhogberg

jhogberg

Erlang Core Team

The default edge names aren’t meant to convey anything: not giving them a name implies that you don’t care what they’re called.

The funny-looking names were most likely chosen because they’re more compact in memory and are unlikely to clash with user-named edges.

stevensonmt

stevensonmt OP

Submitted pull request to hopefully clarify docs a bit.

bjorng

bjorng

Erlang Core Team

Using the {from, to} naming scheme will not work in general, because the :digraph module supports having any number of distinct edges between each pair of vertices.

stevensonmt

stevensonmt OP

What is the utility of that feature? Is it to allow using labels to sort of classify connections in different schemas or something? Something like a graph of cars that includes vertices

v1 = {:toyota, :yellow}
v2 = {:toyota, :red}
v3 = {:ford, :yellow}
v4 = {:also_ford, :yellow}

Could have edges {v1, v2} label: :toyota, {v1, v3} label: :yellow, {v3, v4} label: :yellow, {v3, v4} label: :ford?

bjorng

bjorng

Erlang Core Team

I don’t know the original motivation for that feature, but one algorithm that needs it is Karger’s algorithm.

— All posts loaded —

Where Next? Top

Trending in Questions Top

yarrichar
I’m very new to Elixir, so sorry if this is a silly question: I am wondering what happens to the mailbox of a process when the machine i...
New
Hellowman
Hello everyone! I am new to coding with Elixir/Erlang. And i am looking for some utilities for fuzzing testing like AFL++. Does anyone ...
New
pragdave
How do I tell Hologram not to escape HTML when substituting into templates? {Textile.render(@product.long_description)} escapes the HTM...
New
Fl4m3Ph03n1x
Background When trying to execute mix release on a Windows 11 machine for a Phoenix project I get the following error: * assembling mark...
New
mandar1045
I load tested a plain Phoenix chat app backed by Postgres with 100 million messages in it, everything on default settings, to see what br...
New
rlipscombe
I’d like to create a file with 600 permissions (rw-------), but there’s a race condition if I create it and then change the permissions. ...
New
saleyn
Is there a way to import record definitions in the iex shell for pretty printing (similar to the rr command in the erl shell)? This woul...
New

Other Trending Topics Top

dominicletz
Hey there, I haven’t seen a list of useful Elixir specific skills for the popular AI tools yet so I’m starting one here with my first. ...
New
raa-ziq
Hi everyone :waving_hand: I wanted to share something I’ve been building — NowBlind, a random chat app designed to help people discover ...
New
mudasobwa
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
OndrejValenta
(I just needed to vent somewhere and LinkedIn is full of hope, or hype, I’m not sure which exactly) AI dream has many faces, but general...
New
kip
Localize is the next generation localisation library for Elixir. Think of it as ex_cldr version 3.0. The first version will be released ...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews