laydate | 一款被广泛使用的高级 Web 日历组件，完全开源无偿且颜值与功能兼备，足以应对日期相关的各种业务场景 | Date Time Utils library

We could group by Pair.ID, specify the logical vector in i i.e. whereever there are non-NA elements in 'laydate' and create the new column 'experience' by assinging (:=) the sequence of rows

Your problem is, that the editMode variable does not change when you press the EditButton. No matter in what state, in your CellRow the editMode variable always returns .inactive. I don't know why, it could be a bug. I had the same problem, but I found this question here: SwiftUI - How do I make edit rows in a list?, which uses a workaround by passing the editMode environment value into a private @State variable, which seems to work perfect.

So here is what you need to do:

• Add @State private var editMode: EditMode = .inactive to your EggList view.

  This creates a state variable that from now on holds the editing mode.

• Add .environment(\.editMode, self.$editMode) somewhere after the .navigationBarItems(...).

  This sets the environment variable editMode in EggList to a binding of the state variable above.

• Add .environment(\.editMode, self.$editMode) directly after the CellRow(...) initializer.

  This inserts the state variable editMode into the environment of CellRow, where it can be accessed via @Environment(\.editMode).

Now you can just wrap one of your elements in an if-statement to hide it when in editing mode:

The main disadvantage of the tuple in your case is tuples can not conform protocols like Identifiable.

Another one is that you can change struct to class to make your eggs reference type later, but it's hard for doing that for a tuple and needs lots of changes.

Note: Almost all iOS frameworks contains Foundation, don't import it again.