# Nushell core team meeting 2023-12-20
## Attendees
- Antoine
- Darren
- Ed
- Stefan
- Michael
- AucaCoyan
- Sophia

## Agenda
- [ ] Nupm: avoid `use ../../foo/bar.nu`
- [x] 0.90
- [ ] `--`
- [x] Stack clones https://github.com/nushell/nushell/pull/11288
- should the stack of Stacks be a linked list instead of always calling Stack.clone()?
- [x] logo contest ([nushell/nushell.github.io#1180](https://github.com/nushell/nushell.github.io/pull/1180))
- [x] spread operator [11289](https://github.com/nushell/nushell/pull/11289)
## Discussed Topics

### Stabilization steps

Sophia: picking a version that announces stabilization for core sets
Kubouch: listing of categories how stable certain things are

Spreadsheet time?
Stefan: spell out what is ready with each upcoming release
Ed?: what are parts that get stabilized with the headline of the command. Are all options included.
- goal all options/flag are part of the stability guarantee.

Michael?: how would new-nu-parser be colliding with ongoing work to stabilization
- Sophia: new-nu-parser should follow existing nushell

AucaCoyan: Will there be a 2.0?

#### What is stability?

[Stabilization policy considerations](/TpRSgZmHSdeBfHG3WMP2og)

- scripts
- internal APIs
- interactive use details
- plugin API
- plugins are currently underpowered as they can't run block/access data
- plugin protocol
- vs. crates we provide for plugin authors

Nightly?

### Tangetn: Error make semantics
Red flags
catching and rethrowing effectively impossible right now
errors as values is not yet fleshed out
- structure

### `--` flag fence

active topic, frequently requested
wait for kubouch

### Stack clone

PR: https://github.com/nushell/nushell/pull/11288

slowdown when there is a large datastructure in scope

isolation/perf balance

cow structure of the stack as a potential solution
Sophia: How are things working with closure vs block sharing -> we have semantics of capture/mutation

### Logo contest

Antoine prepared announcement

Feedback: simplify/open the priming themes

### spread operator in call sites

Contentious issue how should positional or optional positional params be treated.
- runtime spreading of positionals possible or not?
- optionals?
- refine examples on existing PR and discuss pitfalls there

Spreading of named arguments through records opens extra complexities

## Not discussed topic

- import patterns (wait for Kubouch)

## Issues
> :bulb: the issues which [needs-core-team-attention](https://github.com/nushell/nushell/labels/needs-core-team-attention)

> :bulb: **Note**
> to list all the PRs currently [opened in `nushell/nushell`](https://github.com/nushell/nushell/pulls):
> ```nu
> gh pr list --json url,number,author,title
> | from json
> | each {|i|
> $"- [($i.number)]\(($i.url)\) ($i.title) \(@($i.author.login)\)"
> }
> | reverse
> | to text
> ```