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

Fix #111: wl/start etc return value #121

Merged
merged 6 commits into from
Sep 27, 2024
Merged

Conversation

holyjak
Copy link
Member

@holyjak holyjak commented Sep 20, 2024

Issue: An inexperienced user may not know what the return value of nil means.

Fix: Be explicit and return a map with :status :ok and perhaps additional info. E.g. wolfram version seems useful.

Issue: An inexperienced user may not know what the return value of nil means.

Fix: Be explicit and return a map with `:status :ok` and perhaps additional info. E.g. wolfram version seems useful.
@holyjak holyjak marked this pull request as draft September 20, 2024 16:54
@holyjak

This comment was marked as resolved.

@holyjak holyjak marked this pull request as ready for review September 20, 2024 17:03
Throw an error if Get fails, e.g. b/c the package does not exist.
Return the alias symbol on succesful load.
@light-matters
Copy link
Contributor

Works well at my end. I had to do the tests manually though as there seems to be something wrong with the namespace detection (probably an Emacs setup bug).

How do you feel about adding an exclamation mark to the end of start,restart etc. though? I know that last time it was deemed unnecessary, but somehow I miss the consistency with side-affecting operations.

@holyjak
Copy link
Member Author

holyjak commented Sep 24, 2024

No strong feelings here. If you really want it, we can change it. Will need to update docs...

@light-matters
Copy link
Contributor

Let's do it. I know it seems like an awkward use of time, but it would help my mild OCD :).

@light-matters
Copy link
Contributor

I can do it later or tomorrow morning.

@holyjak
Copy link
Member Author

holyjak commented Sep 26, 2024

just remember to run tests and build site on this branch, before merging...

@holyjak
Copy link
Member Author

holyjak commented Sep 27, 2024

I do not like eval!. Yes, it is side-effecting, since it can set global vars in Wolfram. But it seems too extreme to have ! there. It is st. else then starting/stopping an external process, as start! does...

@light-matters
Copy link
Contributor

light-matters commented Sep 27, 2024

I do not like eval!. Yes, it is side-effecting, since it can set global vars in Wolfram. But it seems too extreme to have ! there. It is st. else then starting/stopping an external process, as start! does...

Yep, I thought it was more controversial and I hesitated, but made it a separate commit to make it easy to remove. I don't really see the problem with it, but it's true that it's not always side-affecting. Ironically, I would like to find a shorter way to call it and I was thinking that using wl/! as an alternative to eval would be more ergonomic when playing with different expressions.

@light-matters
Copy link
Contributor

Think that's it reset.

@light-matters
Copy link
Contributor

tests and website seem to run, but I discovered a bug (in the public site) that I'll post an issue for.

@holyjak holyjak merged commit 1693a08 into main Sep 27, 2024
@holyjak holyjak deleted the feat-111-start-return-val branch September 27, 2024 12:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants