Skip to content

Conversation

@MaxDesiatov
Copy link
Contributor

Motivation:

GraphLoadingNodes in the same graph always use same file system instance, there's no need to store references to it in each node.

Modifications:

Removed fileSystem property on GraphLoadingNode, as it also simplifies Equatable and Hashable implementations on this type.

Result:

GraphLoadingNode is now a true value type, with no need to define Equatable and Hashable manually on it.

`GraphLoadingNode` in the same graph always use same file system instance, there's no need to store references to it in each node. We should remove this property, as it also simplifies `Equatable` and `Hashable` implementations on this type.
@MaxDesiatov MaxDesiatov added the no functional change No user-visible functional changes included label Dec 1, 2023
@MaxDesiatov MaxDesiatov self-assigned this Dec 1, 2023
@MaxDesiatov
Copy link
Contributor Author

@swift-ci test

@MaxDesiatov MaxDesiatov enabled auto-merge (squash) December 1, 2023 15:47
@MaxDesiatov MaxDesiatov merged commit fd46cdc into main Dec 1, 2023
@MaxDesiatov MaxDesiatov deleted the maxd/remove-graphloadingnode-filesystem branch December 1, 2023 19:39
MaxDesiatov added a commit that referenced this pull request Dec 2, 2023
### Motivation:

`GraphLoadingNode`s in the same graph always use same file system
instance, there's no need to store references to it in each node.

### Modifications:

Removed `fileSystem` property on `GraphLoadingNode`, as it also
simplifies `Equatable` and `Hashable` implementations on this type.

### Result:

`GraphLoadingNode` is now a true value type, with no need to define
`Equatable` and `Hashable` manually on it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no functional change No user-visible functional changes included

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants