MCPcopy Create free account

hub / github.com/Polkadot-Blockchain-Academy/pba-qualifier-exam / types & classes

Types & classes29 in github.com/Polkadot-Blockchain-Academy/pba-qualifier-exam

↓ 1 callersClassCalorie
src/h_advanced_traits.rs:14
ClassBritishEngine
Define the following struct such that it only provides energy if the fuel's output type is `BTU`. It has perfect efficiency.
src/h_advanced_traits.rs:237
ClassCustomMixed
Now think about how you can make the mixer configurable, such that it would produce a new fuel with an energy density that is more influences by one t
src/h_advanced_traits.rs:199
ClassDiesel
src/h_advanced_traits.rs:55
ClassEmployee
src/e_common_traits.rs:10
ClassEmployeeBuilder
First, let's build a naive builder. This builder should allow you to build an [`Employee`], where the `name` and `uid` must be initialized, but the `e
src/m_builder.rs:39
ClassFibonacci
src/f_iterators.rs:54
InterfaceFuel
A technology for storing energy for later consumption.
src/h_advanced_traits.rs:45
ClassFuelContainer
A container for any fuel type.
src/h_advanced_traits.rs:80
InterfaceGet
Next, write a macro that implements a `get` function on a type. Observe the following `trait Get`. It is merely a way to convey a value of type `T` v
src/k_macros.rs:44
ClassGreenEngine
Define the following struct such that it only provides energy if the fuel is `IsRenewable`. It has perfect efficiency.
src/h_advanced_traits.rs:226
ClassIdentified
A unique type explicitly representing an employee that has been identified.
src/m_builder.rs:98
ClassInternalCombustion
A combustion engine that can only consume `Diesel`. The `DECAY` const must be interpreted as such: per every `DECAY` times `provide_energy` is called
src/h_advanced_traits.rs:146
InterfaceIsRenewable
Some traits are just markers. They don't bring any additional functionality anything, other than marking a type with some trait.
src/h_advanced_traits.rs:220
ClassJoule
src/h_advanced_traits.rs:12
ClassLithiumBattery
src/h_advanced_traits.rs:63
ClassMixed
A type that can wrap two different fuel types and mix them together. The energy density of the new fuel type is the average of the two given, once co
src/h_advanced_traits.rs:179
ClassNamed
A unique type explicitly representing an employee that has been named.
src/m_builder.rs:91
ClassNotNamed
A unique type explicitly representing an employee that NOT has been named.
src/m_builder.rs:95
ClassNuclearReactor
A nuclear reactor that can only consume `Uranium` and provide energy with 99% efficiency.
src/h_advanced_traits.rs:134
ClassOmniGenerator
A hypothetical device that can, unlike the `InternalCombustion`, consume **any fuel** that's of type `trait Fuel`. It can provide a fixed efficiency r
src/h_advanced_traits.rs:164
EnumOutcome
src/i_extension_traits.rs:4
InterfaceOutcomeCount
src/i_extension_traits.rs:40
InterfaceProvideEnergy
Something that can provide energy from a given `F` fuel type, like a power-plant.
src/h_advanced_traits.rs:101
ClassSeven
src/k_macros.rs:48
InterfaceToBTU
src/h_advanced_traits.rs:268
ClassTypedEmployeeBuilder
A new builder that uses the "type-state" pattern to ensure that the user has set the name and uid. The main trick here is that instead of having `name
src/m_builder.rs:141
ClassUnIdentified
A unique type explicitly representing an employee that has NOT been identified.
src/m_builder.rs:102
ClassUranium
src/h_advanced_traits.rs:71