Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Repl :t command doesn't work with (use) #1460

Open
ekzhang opened this issue Dec 3, 2023 · 3 comments
Open

Repl :t command doesn't work with (use) #1460

ekzhang opened this issue Dec 3, 2023 · 3 comments
Labels

Comments

@ekzhang
Copy link

ekzhang commented Dec 3, 2023

I think the REPL's :t command doesn't quite work as I would expect with namespaces that are opened!

Here's the output on carp-v0.5.5-x86_64-macos:

鲤 :t IO.read-file
=> (Fn [(Ref String <a>)] (Result String String) <StaticLifetime>)
鲤 (use IO)
鲤 :t read-file
I can’t find the symbol `read-file` at REPL:5:7.

Traceback:
  (type read-file) at REPL:5:1.

This is despite that I can otherwise call (read-file) directly after (use IO) works. The same happens in composition when I type use IO:

鲤 use IO
=> IO
鲤 :t (read-file "input")
Can't get the type of: (read-file "input") at REPL:2:7.

Traceback:
  (type (read-file "input")) at REPL:2:1.
鲤 :t (IO.read-file "input")
=> (Result String String)

But not with (use IO) — I'm not sure what the difference is here.

鲤 (use IO)
鲤 :t (read-file "input")
=> (Result String String)
鲤 :t (IO.read-file "input")
=> (Result String String)
@scolsen scolsen added the bug label Dec 4, 2023
@KoltPenny
Copy link

Is this project dead?

@eriksvedang
Copy link
Collaborator

@KoltPenny Hi, I wouldn't say that it's dead but it's very much on the back burner right now.

I'm the head maintainer of the project, and I'm currently working on a (commercial) game project (https://www.eriksvedang.com/2024/02/26/announcing-manahex.html), with more in the pipeline. I hope to be able to take the time off to work on "Carp 2.0" sometime in the future. Such a project was started, using LLVM, and it showed much promise but didn't reach feature parity with what's in this repo, and is thuse kept private for now. Until more active work is resumed, it seems unlikely that the project here will progress much. Feel free to try it out though, any feedback is appreciated! Even PRs could be interesting, as long as they're not too large.

Cheers,
Erik

@KoltPenny
Copy link

@eriksvedang Thanks! Your new game looks great btw.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants