stevensonmt
Was hoping someone could take a look at this code and advise me on any organizational pitfalls or algorithm inefficiencies. I would also appreciate if someone could confirm that what I think is a depth first search algorithm is actually so. Thanks in advance for taking the time to look.
This was a solution to the exercism exercise “Connect”. I’m somehow locked from requesting mentor feedback on exercism because some request from probably two years ago is still unanswered and there is no way to cancel it that I can find.
defmodule Connect do
@doc """
Calculates the winner (if any) of a board
using "O" as the white player
and "X" as the black player
"""
@spec result_for([String.t()]) :: :none | :black | :white
def result_for(board) do
board
|> process_input()
|> find_winner()
end
defmodule Board do
@moduledoc """
Creates graph consisting of vertices with edges. Build Paths with respect to obstacles (vertices of other color or empty).
"""
defstruct vertices: %{}, edges: %{}, rows: 0, cols: 0
@type path :: [{integer, integer}]
@type player :: :black | :white | :none
@spec add_vertex(%__MODULE__{}, {integer, integer, player}) :: %__MODULE__{}
def add_vertex(board \\ %__MODULE__{}, {x, y, player}) do
%__MODULE__{
board
| vertices: Map.update(board.vertices, player, [{x, y}], fn curr -> [{x, y} | curr] end)
}
end
@spec add_edge(%__MODULE__{}, player, {{integer, integer}, {integer, integer}}) ::
%__MODULE__{}
def add_edge(board, player, edge = {{x1, y1}, {x2, y2}}) do
cond do
# same row, one col on either side ok
x1 == x2 and :erlang.abs(y1 - y2) == 1 ->
update_edges(board, player, edge)
# comparing to row above, one col to left or same col ok
x1 - x2 == 1 and (y1 - y2 == 0 or y1 - y2 == 1) ->
update_edges(board, player, edge)
# comparing to row below, one col to right or same col ok
x1 - x2 == -1 and (y1 - y2 == 0 or y1 - y2 == -1) ->
update_edges(board, player, edge)
true ->
board
end
end
def update_edges(board, player, {{x1, y1}, {x2, y2}}) do
%__MODULE__{
board
| edges:
Map.update(board.edges, player, [{{x1, y1}, {x2, y2}}], fn curr ->
[{{x1, y1}, {x2, y2}} | curr]
end)
}
end
def add_edge(board, _) do
board
end
@spec add_edges(%__MODULE__{}) :: %__MODULE__{}
def add_edges(board) do
board.vertices
|> Enum.map(fn {player, vrtcs} ->
{player,
for v1 <- vrtcs,
v2 <- vrtcs,
:uniq do
{v1, v2}
end}
end)
|> Enum.reduce(board, fn {player, edges}, bd ->
edges
|> Enum.reduce(bd, fn edge, b ->
add_edge(b, player, edge)
end)
end)
end
@spec rows([{integer, integer, player}]) :: integer
def rows(vertices) do
vertices
|> Enum.group_by(fn {x, _, _} -> x end)
|> Enum.count()
end
@spec cols([{integer, integer, player}]) :: integer
def cols(vertices) do
vertices
|> Enum.group_by(fn {x, _, _} -> x end)
|> Enum.take(1)
|> Enum.map(fn {_, row} -> length(row) end)
|> hd
end
@spec build_board([{integer, integer, player}]) :: %__MODULE__{}
def build_board(vertices) do
rows = rows(vertices)
cols = cols(vertices)
vertices
|> Enum.reduce(%__MODULE__{rows: rows, cols: cols}, fn v, acc ->
add_vertex(acc, v)
end)
|> add_edges()
end
@spec find_winner(%__MODULE__{}) :: path | nil
def find_winner(board) do
Enum.find([:black, :white], :none, fn player ->
try do
dfs(board, player)
|> hd
rescue
_ -> false
end
end)
end
def dfs(board, player) do
potential_starting_points = starting_points(board, player)
potential_end_points = end_points(board, player)
board.edges
|> Map.get(player)
|> Stream.filter(fn {v1, _v2} ->
Enum.member?(potential_starting_points, v1)
end)
|> Stream.flat_map(fn {v1, v2} ->
__MODULE__.build_path(board, player, [v2, v1], potential_end_points)
end)
|> Enum.take(1)
end
defp starting_points(board, :black) do
0..(board.rows - 1)
|> Enum.map(fn i -> {i, i} end)
end
defp starting_points(board, :white) do
0..(board.cols - 1)
|> Enum.map(fn c -> {0, c} end)
end
defp end_points(board, :black) do
rows = board.rows
cols = board.cols
0..(rows - 1) |> Enum.zip((cols - 1)..(cols - 1 + rows - 1))
end
defp end_points(board, :white) do
rows = board.rows
cols = board.cols
(rows - 1)..(cols + rows - 2)
|> Enum.map(fn c -> {rows - 1, c} end)
end
@spec build_path(%__MODULE__{}, player, path, [{integer, integer}]) :: path | nil
def build_path(board, player, path, potential_end_points) do
start_from = hd(path)
if Enum.any?(potential_end_points, fn {a, b} -> Enum.member?(path, {a, b}) end) do
[%{winner: player, winning_path: path}]
else
board.edges
|> Map.get(player)
|> Stream.filter(fn {v1, v2} ->
not Enum.member?(path, v2) and v1 == start_from
end)
|> Stream.flat_map(fn {_v1, v2} ->
build_path(board, player, [v2 | path], potential_end_points)
# doesn't recurse infinitely b/c eventually the filter yields empty
# data to the flat_map call
end)
end
end
end
@spec process_input(String.t()) :: %__MODULE__.Board{}
defp process_input(input) do
input
|> Enum.with_index()
|> Enum.flat_map(fn {line, row} ->
line
|> String.graphemes()
|> Enum.with_index()
|> Enum.map(fn {c, col} ->
{row, row + col, c}
end)
|> chars_to_players
end)
|> Board.build_board()
end
@spec chars_to_players([{integer, integer, String.t()}]) :: [{integer, integer, atom}]
defp chars_to_players(positions) do
positions
|> Enum.map(fn {x, y, char} ->
{x, y,
case char do
"X" -> :black
"O" -> :white
_ -> :none
end}
end)
end
defp find_winner(board) do
cond do
# no edges implies single vertex, just return the player that owns that vertex
board.edges == %{} ->
winner =
board.vertices
|> Map.keys()
|> hd
# if the only vertex owner is :none, the winner is :none
board.vertices |> Map.keys() == [:none] ->
:none
# find the winner or return :none if no winning path found
true ->
Board.find_winner(board)
end
end
end
Trending in Discussions
The obligatory hello world thread!
Who are you and where are you from? :stuck_out_tongue:
New
Hey there,
It’s been more than a year since we started using LiveView as our main UI library and building a whole library of UI componen...
New
Hey folks,
I wanted to share with you a project I’ve been working on for a while: It’s an Open Source (AGPLv3) newsletter tool. Think Ma...
New
Hi everyone :waving_hand:
I wanted to share something I’ve been building — NowBlind, a random chat app designed to help people discover ...
New
In my third year of college, around 2010, I found Erlang. A few years later, I found Elixir. I liked the ideas at once: many small proces...
New
Hi everyone,
I have 8 years of production experience with Erlang/OTP and I’m just starting to get to know Elixir. What would you learn f...
New
I’ve been tinkering with Lynx (by José) via hold_ledger. I used AI to write the code, a separate specification, the tests, and the Lean p...
New
Other Trending Topics
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
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
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
New
(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
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
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself.
My main conc...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #code-sync
- #discussion
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #elixirconf-us
- #blog-post
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #elixirconf-eu
- #processes
- #security
- #api
- #forms
- #performance










Showing Posts 1 to 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
Sebb
Do you know about mentored mode in exercism?
https://exercism.io/mentored-mode-vs-independent-mode
stevensonmt
Yes, but in general I prefer to work through the exercises on my own in a random order. I know that for other tracks mentors can be overwhelmed by the queue of exercises awaiting mentoring. I’d prefer not to contribute to that issue if possible.
tovarchristian21
I think that is the jist of exercism, if you are looking for people who are actually willing to review your code and give you advice, there is not a better place than the actual mentored mode in exercism.
stevensonmt
It’s rare for me to encounter an exercise where I want that feedback. I appreciate the suggestion, but I really do understand how exercism works. The fact that I am locked from requesting feedback on this particular exercise because of an outstanding request from at least 7 months ago reinforces my desire not to clutter up the mentoring queue. Again thanks for your suggestion but this is not an XY problem.