Interface SingleSlotStorage<T>
- Type Parameters:
T
- The type of the stored resource. Experimental feature, we reserve the right to remove or change it without further notice. The transfer API is a complex addition, and we want to be able to correct possible design mistakes.
- All Superinterfaces:
Storage<T>
,StorageView<T>
- All Known Implementing Classes:
FullItemFluidStorage
,SingleFluidStorage
,SingleStackStorage
,SingleVariantItemStorage
,SingleVariantStorage
-
Method Summary
Modifier and TypeMethodDescriptiondefault Iterator<StorageView<T>>
iterator
(TransactionContext transaction) Iterate through the contents of this storage, for the scope of the passed transaction.Methods inherited from interface net.fabricmc.fabric.api.transfer.v1.storage.Storage
exactView, extract, getVersion, insert, iterable, simulateExtract, simulateInsert, supportsExtraction, supportsInsertion
Methods inherited from interface net.fabricmc.fabric.api.transfer.v1.storage.StorageView
extract, getAmount, getCapacity, getResource, isResourceBlank
-
Method Details
-
iterator
Description copied from interface:Storage
Iterate through the contents of this storage, for the scope of the passed transaction. Every visitedStorageView
represents a stored resource and an amount. The iterator doesn't guarantee that a single resource only occurs once during an iteration.The returned iterator and any view it returns are only valid for the scope of to the passed transaction. They should not be used once that transaction is closed.
More precisely, as soon as the transaction is closed,
hasNext()
must returnfalse
, and any call tonext()
must throw aNoSuchElementException
.Storage.insert(T, long, net.fabricmc.fabric.api.transfer.v1.transaction.TransactionContext)
andStorage.extract(T, long, net.fabricmc.fabric.api.transfer.v1.transaction.TransactionContext)
may be called safely during iteration. Extractions should be visible to an open iterator, but insertions are not required to. In particular, inventories with a fixed amount of slots may wish to make insertions visible to iterators, but inventories with a dynamic or very large amount of slots should not do that to ensure timely termination of the iteration.
-