Thanks for the insight!
I did not want to marry the medicine tight and I need wings to make microcircuits out of them.
I am to rethink it again, though. Thanks!
mudasobwa
Creator of Cure
christhekeele
FWIW while this is internationally and historically correct, this subtlety has been eroded in modern US iconography over the last 125 years. My medical alert tattoo has the caduceus because more medical professionals recognize it over the rod of Asclepius as a medical sigil, laypeople doubly so.
1
mudasobwa
Creator of Cure
Thanks for the counterinsight!
Caduceus it is for now then. Explicitly taking into account I already have a free promotion of the language on your chest 
2
mudasobwa
Creator of Cure
I am back, working on Cure.
The license (Apache2, same as Elixir) is added. To run examples do make clean && make all in the project folder and then ./run_cure.sh examples/14_pipe.cure. The handy compilation/running is pending.
What’s There
▸ Pipes are monadic (see https://github.com/am-kantox/cure-lang/blob/main/examples/14_pipe.cure ). 5 |> double() would return Ok(10) assuming def double(x: Int): Int = x * 2, Ok(5) |> double() too. Error(“Nah”) as LHO would not attempts to call RHO and would be propagated.
▸ Peano arithmetics Nat declared as Succ(Succ(…(Zero))) is there, although I am not sure I am to keep it. Int and Float are to be [most likely] ditched in favor of Number.
▸ List and Vector are fully functional.
▸ Ok(T), Error(E), Result(T, E), etc.
Questions
▸ Shall I create kinda google group in addition to GH Discussions? I am not a big fan of groups myself.
▸ Shall I continue with typeclasses which are half-done or there is something more expected?
▸ What kind of tooling should come first (now the compilation is awkward.)
▸ Shall I make LSP fully robust before anything else (including SMT solver intergration)?
Thanks.
2
Asd
- Make
make testworking - Reduce noise in compiler output
- Fix compiler errors locations
Outputsmodule Playground do export [main/0] def main(): Int = 1 + def() endError: Parsing failed: {parse_error,{unexpected_token_in_expression,def},0,0} - Fix and test the very very basics of your language
Outputsmodule Playground do export [main/0] def main(): Int = 1 + f() def f(): Int = 3 endError: Type Checking failed: {type_check_failed, [{typecheck_error,"Failed to infer function body type", {location,4,3,undefined}, {inference_failed, {constraint_solving_failed, {unification_failed, {primitive_type,'Int'}, {function_type,[],{primitive_type,'Int'}}}}}}]}
I’ve been looking at the project since it’s release and it looks like most of it was generated without any testing. I’ve pulled it 3 times and make test never worked while make all worked just once, a week after it’s initial post on the forum. I would consider fixing bugs, creating CI and all of that before implementing new features
3
mudasobwa
Creator of Cure
Thanks!
Added to my own pipeline (and fixed.)
Not yet, sorry. I use it.
This is WIP. Some are already correct. This is currently top priority.
Ugh. Done.
Sorry for wasting your time.
I am not sure what does mean “generated,” I have tried Chez Scheme on the very early stages to generate code, but I failed. I use jujutsu as a home CVS and git exports might be creepy, I suppose. Tagged versions should compile though.
I doubt a comprehensive CI would have helped me in any way on the current stage, sorry. I even do not have a robust way to avoid full stdlib recompilation atm. And the new features is something I am after right now not because I love features for the sake of features, but because I manage to produce BEAMs and use them.
2
michallepicki
I am 100% agreeing with @Asd and I think by “generated” they mean “generated by an AI agent”. For example, when the commit message says “All tests are passing”, the tests were not actually passing 
From my point of view it would help me see which commit is “good” and can be checked out locally to poke around, because so far I only wasted some time and learned nothing about the capabilities of the language / typesystem etc
2
mudasobwa
Creator of Cure
Ah, commit messages are AI-generated, yes. Well, many of them.
I am to probably invest some time into automating jujutsu git export strategy. CI won’t be there until 2026 Jan, sorry.
0
NobbZ
What do you even mean by “git export strategy”?
I use jj for about 6 weeks now, and interacting with git repositories feels natural and seamless. I don’t have to have any strategy, I just push my changes…
0
mudasobwa
Creator of Cure
I don’t interact with those per se, I use jj git export and I believe some commits on that stage should better go into git branches, or like, because I do not bother to keep the jujutsu repo clean in general.
0