# Nushell core team meeting 2025-04-23
## Attendees
- Stefan
- Bahex
- Jack
- Piet
- Storm
- Amtoine
- Douglas
- Loic329
- Darren
- Jan9103

## Agenda
- [X] `try {} finally {}` value semantics [discord](https://discord.com/channels/601130461678272522/1353434388938883143/1364421393407803402)

    $IN
    | try {
        # <== $IN
        ...
        # ==> $SUCC / $ERR
    } catch {
        # <== $ERR
        ...
        # ==> $CATCH
    } else {
        # <== $SUCC
        ...
        # ==> $ELSE
    } finally {
        # <== $CATCH / $ELSE
        ...
        # ==> $FINALLY
    }
    # ==> $FINALLY

If a block is not given, it acts as if it's an empty block (i.e. returning its input as it is)
- [ ] `update` with multiple columns vs `update cells`
[Some considerations](https://github.com/nushell/nushell/issues/15477#issuecomment-2774994864)

    def update [
        fields: one_of(cell-path, list<cell-path>),
        replacement: any
    ]

    | update field_a {|| ...}
    | update [field_a field_b] {|| ...}

Would this be useful?
- [ ] .

## Discussed Topics
- `try {} finally {}`
- not entirely against it
- but `complete` for nu commands would probably be a better fit
- `return` inside `try` is already not handled well, this would be more confusing
- => Try to build a `complete` for nu commands and see if we like that