language commands and which are not required for the language?cargo publish
winget-create created a wrong manifest
Justin and Darren fixed the manifest
Justin submitting the new version caused rejection due to different source repo.
Patch releases didn't get released as well.
most of the "language" is currently defined as commands. (e.g. let, def)
Should environment be part of the core language?
Seems to be very shell specific (currently deeply embedded in the engine state)
but is our way to encode global state (is global state considered evil?)
having the data parsing logic is part of the nu magic (the std library?)
Role of overlays?
JT: more shell specific
Jakub: core part of the language in the parser currently.
Fernando: python envs are outside the scope of the language (you set up what is available but import in the script in a second step)
Runtime/Engine
The shell has to be able to execute external commands, do syscalls.
Might not be necessary to build a DSL (domain specific language) with nu semantics (e.g. for data analytics, data manipulation)
API/ABI boundaries
Important Who defines/How is the API for commands defined?
We need both flexibility and API stability
Q: Can we get a versioned command signature for 0.80
2 days before the release
General sentiment positive (we had no bad surprises with this release)
What is our post freeze strategy
Discipline about tagging the develop version number to more easily identify bug reports.
Who wants to automate that?
Darren has the contribution counting script with the mailmap files (keep those private among maintainers)
github board for tracking the 0.80 progress probably better integration. Notion nicer to write or link different stuff
Our github issue tracker needs more granular label. Probably community effort needed to tag and triage old issues.
breaking changes that are semantically together should land together
But we shouldn't rush other changes that might break as they are not yet tested well enough, as something is already ready (source-env is already ready)
-> can we land source-env in the current semantics?
or
or
By clicking below, you agree to our terms of service.
Sign in with Wallet
New to HackMD? Sign up
| Syntax | Example | Reference | |
|---|---|---|---|
| # Header | Header | 基本排版 | |
| - Unordered List |
|
||
| 1. Ordered List |
|
||
| - [ ] Todo List |
|
||
| > Blockquote | Blockquote |
||
| **Bold font** | Bold font | ||
| *Italics font* | Italics font | ||
| ~~Strikethrough~~ | |||
| 19^th^ | 19th | ||
| H~2~O | H2O | ||
| ++Inserted text++ | Inserted text | ||
| ==Marked text== | Marked text | ||
| [link text](https:// "title") | Link | ||
|  | Image | ||
| `Code` | Code |
在筆記中貼入程式碼 | |
| ```javascript var i = 0; ``` |
|
||
| :smile: |  |
Emoji list | |
| {%youtube youtube_id %} | Externals | ||
| $L^aT_eX$ | LaTeX | ||
| :::info This is a alert area. ::: |
This is a alert area. |
On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?
Please give us some advice and help us improve HackMD.
Syncing
-
Any changes
Be notified of any changes
-
Mention me
Be notified of mention me
-
Unsubscribe
Subscribe