Nushell core team meeting 2023-05-24

Attendees

• Darren
• JT
• Storm
• Wind
• Antoine

Agenda

• make the standard library a true directory-based module on the filesystem?
  • reduce startup time as we do not need to parse all the library
  • solve a ton of issues (see #standard-library)
  • can use hash of the library to make sure the files are ok
• what topics for the mini design meetings?
  • config
  • engine
  • parser
  • stdlib
  • commands
  • …
• revisit crate names (again) and discuss nu-cmd-extra strategy
• Path to 1.0 completeness and bugfixes
• commands (spreadsheet here)

Discussed Topics

Standard library

• JT: what if we precompile the standard library?
• Antoine: What if we parse lazily? (we only need prelude at the beginning)

Config update issue

• #9264
• Needs investigation to understand if table-related or engine-related

Crate names

• Use nu-cmd-extra (and unsupported commands will go there)

We agreed to move the following commands to nu-cmd-extra

​​​​- bits
​​​​- bytes
​​​​- math

By definition commands in nu-cmd-extra will not be in 1.0

PR's

gh pr list --json url,number,author,title
| from json
| each {|i|
    $"- [($i.number)]\(($i.url)\) ($i.title) \(@($i.author.login)\)"
}
| reverse
| to text