benonymus
Hey,
I started to play around with the ok_jose library in a project, and when I compile the code I get these warnings:
warning: this clause cannot match because a previous clause at line 73 always matches
Warning: lib/projx/sessions/schemas/session.ex:145warning: this clause cannot match because a previous clause at line 73 always matches
Warning: lib/projx/sessions/schemas/session.ex:158warning: this clause cannot match because a previous clause at line 73 always matches
Warning: lib/projx/sessions/transcripts.ex:195
The lines it is pointing to is where I have |> Pipe.ok(),
but where it says the previous clause is, there is nothing, in one file comments for example, other completely other function.
If I remove |> Pipe.ok() the warning goes away.
if I remove the use OkJose the warnings go away as well, but that results in new problems.
I am on elixir:1.13.1
Any ideas?
I also tried this in a new empty project, but no issues there for now.
Thanks
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Catch errors, track performance, monitor hosts and more.
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
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
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.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
**Building the future of software with AI, trust, and human connection.**
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 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
Nicd
It seems
Pipe.okcompiles to a case statement of some sort: ok_jose/lib/ok_jose/def_pipe.ex at 2840d629a47bb7ed1f0339e422b571671639d468 · vic/ok_jose · GitHub so I assume it has clauses that are ordered badly or something similar.In fact I see there has been a similar problem earlier also: Warning during compile · Issue #1 · vic/ok_jose · GitHub
benonymus
Yeah, I decided due to time constraint to switch to GitHub - CrowdHailer/OK: Elegant error/exception handling in Elixir, with result monads. · GitHub for now. Thanks for checking!