fn foo(x: i32) {
match x {
const { 3.pow(3) } => println!("three cubed"),
_ => {}
}
}
But it looks like inline_const_pat
is still unstable, only inline_const
in expression position is now stabilized.
fn foo(x: i32) {
match x {
const { 3.pow(3) } => println!("three cubed"),
_ => {}
}
}
But it looks like inline_const_pat
is still unstable, only inline_const
in expression position is now stabilized.
It's because it has to work in pattern contexts as well, which are not expressions.
According to Wikipedia:
In March or April 2023, it dimmed to magnitude 12.3. A similar dimming occurred in the year before the 1946 outburst, indicating that it will likely erupt between April and September 2024.
You can give chisel a try. It tunnels all traffic over http/https, and the client can then create port forwards, just as with ssh, to access other services.
Yes, for example, syncing on a kernel panic could lead to data corruption (which is why we don't do that). For the same reason REISUB is not recommended anymore: The default advice for a locked-up system should be SysRq B.
https://linux-tc-notes.sourceforge.net/tc/doc/cls_u32.txt:
The base operation of the u32 filter is actually very simple. It extracts a bit field from a 32 bit word in the packet, and if it is equal to a value supplied by you it has a match. The 32 bit word must lie at a 32 bit boundary.
You should not torrent over the tor network, but you can torrent over the I2P network. qBittorrent even has experimental I2P support built in.
It's the Schmidtstedter Knoten in Erfurt.