Good vs. Evil
- Thread starter Randomguy404
- Start date
-
The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord
22. I'm feeling tired and generally low, but I'm supposed to be playing D&D tonight. I'm gonna go because I know I'll regret it if I don't.
21 I managed to work on Arena_keeper a bit more.
Module system is now almost done. I only need to make sure that mods don't trample over each other and add 1 thing back in and its done. After that, I simply need to clean up the code and update the README and it can be merged.
Working on this also caused me to discover something new about rust's syntax, to do with enums and pattern matching.
I already knew that entries in an enum could hold values. However, I always used that like this:
But, today I learned that you can also basically use them like structs and that you can be selective about which fields you want out of them when pattern matching. This means that I only need one branch for every field that the two tile types share (like image, or end) in the above example.
Module system is now almost done. I only need to make sure that mods don't trample over each other and add 1 thing back in and its done. After that, I simply need to clean up the code and update the README and it can be merged.
Working on this also caused me to discover something new about rust's syntax, to do with enums and pattern matching.
Code:
#[derive(serde::Serialize, serde::Deserialize)]
#[serde(untagged)]
enum Tile {
BaseTile {
image: String,
end: f64,
baseSpeed: f64,
},
ExtendingTile {
end: f64,
image: String,
extend: TileType,
baseSpeed: Option<f64>,
},
}
impl Tile {
pub fn get_end(&self) -> f64 {
match &self {
Tile::BaseTile { end, .. } | Tile::ExtendingTile { end, .. } => *end,
}
}
}
Code:
pub enum Example {
NoValue,
OneValue(f64),
TwoValues(f64,i32)
}But, today I learned that you can also basically use them like structs and that you can be selective about which fields you want out of them when pattern matching. This means that I only need one branch for every field that the two tile types share (like image, or end) in the above example.
19 I'll be the third one to welcome back MrMonsterGuy then. Welcome back dude, good to have you playing the forum games again.
19 decided to push what I have for the module system to master.
It should be on feature parity with the old generated code, however mods aren't name spaced and are thus able to trample over each other.
The reason I decided to push is simple, a new GUI library appeared that seems actually rather nice, works on WASM AND it is render agnostic. Meaning that I rather look into that
The library: https://github.com/hecrj/iced
With that I may even be able to bring back the floating window style of the yew based version, if people like that.
It should be on feature parity with the old generated code, however mods aren't name spaced and are thus able to trample over each other.
The reason I decided to push is simple, a new GUI library appeared that seems actually rather nice, works on WASM AND it is render agnostic. Meaning that I rather look into that
The library: https://github.com/hecrj/iced
With that I may even be able to bring back the floating window style of the yew based version, if people like that.
18 I took two test today. Didn’t do too hot on my biology test, but I’m pretty confident in my Algebra 2 test.