#unsizeable

[3416]

just need to give a shoutout to all the people who interact w me or the things i make on here for the love and good vibes. twitter's been pissing me off the past couple days and i just think it reaffirms i'll never really leave tumblr bc the fandom culture here is just so much.. more lol

[restroom]

Dire times are indeed upon us. Scrounged four mall dep't stores today and in the men's section of each one were several arrays of flatcaps.

[kazhanko-art]

I’ve been seeing an uptick in social media posts about the immanent collapse of canada and how it’d be good for us to join the US, particularly by allegedly american accounts. And while not unsizable chunk of it is Canadians, with legitimate anxiety and frustrations (again, I strongly believe the libs and trudeau fucked up a lot and I do not like them) I feel a lot of it might be russian or other bot accounts trying to disrupt Canadian democracy.

This is definitely one of the shakier periods in Canadian politics, and there’s a lot of anxiety and anger around it (both legitimate and illegitimate) but it’s bizarre to act like Canada will fall when this is an average tuesday in multiple european democracies and the American political system has felt like it’s about to collapse forever now, and they’re all still kicking around, so this idea that Canada is exceptionally doomed comes across as being not an entirely organic concern

[xxtc-96xx]

Because of her weak constitution, will Lilac also be an unsized Mewtwo?

I dunno if she will actually, since she’s not premature

[skaruresonic]

idk why so many antis took the whole "like long lost sibling would " on that alt text for the promo of dark beginnings as canon and 'solid evidence' that shadria have a sibling relationship when the text can also be read as sarcastic or mocking? I might be reaching but sarcasm doesn't really translate well in text but putting any indication like ' or () when it doesn't flow in the original text always feels like somebody making snarky comment to me, idk to me personally I could argue w antis that it mocking them by being like 'isn't this obvious ship bait totally platonic' ¯\_(ツ)_/¯

Idk it just so annoying to see so many antis go 'haha shadria fans must be weeping' when it a fucking alt text on a promo that I doubt any writers or higher up would quality check in comparison to the fact in canon that shadria has yet to be label unlike other characters in the series as well as ignoring how many opportunities the series had to outright have shadow call Maria his sister no media be it games, shows or comics has him calling her sister or vice versa. So unless the new game outright has him referring to her as sister in all languages, shadria will still be a valid ship and even if that does happen it still won't erase all the moments the two had either shippers r still gonna ship.

I don't understand why antis think one little text line that not even in any media is gonna make Sharia shipper suddenly stop. Apology for ranting but omg it so annoying seeing anti act so high n mighty over something so trivial 💀

Personally, I'm inclined to agree with Beev on this one. It seems like they threw in "as long-lost siblings would" in order to placate the antis. Which would, ironically enough, imply an awareness that the piece could be read as romantic.

There was really no need for a parenthetical note to dictate the tone of the piece. If they left it at "Shadow and Maria reach out for one another in an infinite abyss," the reader could interpret it any way they want.

(Random tangent, but describing space as an "infinite abyss" also strikes me as a bit strange. You can see stars in the piece.)

I think SoA knows the flavor of the food they've been serving us recently, but they did this as a sort of PR move to cover their asses. They might be worried about losing face with Shadria antis, who form a not-unsizable portion of fandom now compared to Shadria shippers.

...but I mean. Come on. There's no way they're not aware.

And the thing is, it's not like the manga or anything else is explicitly confirming the dynamic is definitely romantic, either. It's not like we shippers aren't aware we have our ship goggles on; we just wanna vibe in our space.

Ever since playing SA2 as a kid and wondering if Shadow was in love with Maria, I've always had the feeling that their dynamic was supposed to be left open to interpretation. Antis want to impose their reading upon pain of accusing you of being a freak, while the shippers are more like "haha... unless?"

Also, it's really funny to think this is the ship they consider worth calling people "demented dogs" over. Have you literally played any other video game ever? Read any book? Watched any movie? Oh no, a ship the game probably wanted us to ship a little! OOGA-BOOGA.

This is probably one of the least problematic ships in existence tbh. Methinks the antis doth protest too much.

Besides, you're (general you) being disingenuous to claim there are no undertones whatsoever. Why include them if the dynamic is only supposed to be interpreted a certain way?

Using Sonic X as an example of what I'm talking about might be cheating, but since it's about as non-canon as the manga appears to be, it seems fair to mention it.

In Sonic X, Shadow also tends to recall Maria through a romanticized filter; he remembers her as being extra beautiful and ethereal compared to other characters who recall her as simply an ordinary girl.

Compare Shadow's flashbacks to the flashbacks of the soldier who shot her:

In the soldier's flashback, Maria is just a frightened child who pulls the lever. We're not shown her body, but rather his reaction:

In Shadow's flashbacks, Maria slumps tragically to the ground and/or lies on the ground, calmly speaking her last words while bathed in soft blue light.

There's a heightened sentimentality to Shadow's memories of Maria which serves to emphasize, I guess, the "beauty" that the ARK tragedy took from him. Considering Shadow is stated to like "nothing," maybe he finds nothing or no one else as beautiful.

Not that her death wasn't tragic in and of itself, but there's a marked difference in tone. One feels like a child's senseless death viewed from the POV of the man who killed her, and the other feels like... to be frank... something romance anime-coded.

It's worth noting that Shadow maintains this romanticized filter even when fantasizing about an alternate timeline where she survived (or perhaps the future they had been looking forward to after she was cured), so you can't always chalk it up to a product of Gerald's brainwashing:

...let's unpack this on the therapist's couch, hmm?

---

I don't understand why antis think one little text line that not even in any media is gonna make Sharia shipper suddenly stop.

Very true, and it's a fool's errand to try. I was going to reblog that piece without tags, as per usual, but I decided to tag it as "Shadria" just to flip antis off. Fuck you, you can't tell me what to ship on my own blog. xP

(also tagged it "Shadria" because "Shadria" was the original ship name and it's still a perfectly good ship name. it's a pet peeve of mine, how antis chased shippers off the Shadria tag and forced them to come up with less elegant portmanteaus. "Shadaria" and "Mariadow" sound so much clunkier than "Shadria")

---

Apology for ranting but omg it so annoying seeing anti act so high n mighty over something so trivial 💀

No worries, antis are annoying at best. Wish they would just go away. >.>

[nohoperadio]

You call big things "sizeable" so you should be able to call little things unsizeable... that should work I think

[scotianostra]

March 20th 1780 the firm of James Watt and Co was established to manufacture the world’s first duplicating machines.

James Watt developed his document copier, which offset a written document by pressure onto thin, translucent, unsized paper to produce a reversed copy from the back, between 1778 and 1780.

His invention was believed to have been stimulated by the tedium he experienced in making copies of correspondence in his business. Adapted in collaboration with Matthew Boulton and James Keir, with whom Watt formed a partnership, for use with either a screw or roller press and using their own special ink, the copier was patented in 1780. By the end of 1780 one hundred and fifty machines had been sold, and six hundred and thirty by the end of the first full year of business.

The portable copying machine was developed by James Watt junior and thus supplied the company with a new machine just at the moment when the patent for the fixed machine expired. By late 1795 the new copier was commercially available, and a pamphlet to accompany it 'Directions for using the patent Portable Copying Machine Invented and Made by James Watt & Co.', was published in the same year.

Successful on its appearance and inspiring several imitators, the Watt copiers are historically important as the start of a tradition of pressure copiers that lasted for most of the nineteenth century.

[idrawprettyboys]

Zuma in his old outfit with the slicked back hair and no eyebrows. He reminds me of Creed from Black Cat! This was bravely drawn straight in Micron pen on unsized Indian watercolor paper, which I have never used before. The paper is extra thick and unpredictably lumpy, yet it handles a micron pen very well!

[kurbcotain]

i rly like that the ce era the thursdat dot net media tab was just a slideshow of unsized ass pictures so you would be scrollin and then boom that big ass pic of andrew shows up. 👋👋 hey girl!!!

[grossillygirl]

GUYS LMFAOOO i made a guy cum and afterwards he said that my tits are so big do i leave them at home and then go out😭 cus theree no way i can carry them LMFAOOOO

And he said my tits are "unsizeable" 😭 funniest thing ever

[tenebristiclov3r]

Helen Frankenthaler, Mountains and Sea, 1952

Oil and charcoal on unsized, unprimed canvas

[scoonsalicious]

If you ever feel so inclined to support my work, hop on over to buy me a coffee; it's much appreciated! <3

Part 1 (05.10.24) Part 2 (06.28.24) Part 3* (07.03.24)

Complete (07.09.24)

Complete (07.11.24)

Complete (07.23.24)

Complete (09.10.24)

Chapter 1: Uncovered (11/18/24) Chapter 2: Unquestioning (11/18/24) Chapter 3, Pt. 1: Unsized (01/10/25)

[tedwillisart]

Threefourone...acrylic on unsized canvas, 30in./76cm. sq., 1'24.

[autisticrustacean]

How I comprehend pointers (in rust)

the main pointer types are:

&T

&mut T

Box<T>

they each have different properties;

&T can read T, but the compiler (borrow checker) statically analyzes your code to make sure that no writes occur to the pointee while there is a reference to it.

&mut T allows mutability, though only by it, and the compiler makes sure nothing reads from T while there is a mutable reference, and that there is only one mutable reference to T at at time.

Box<T> is fairly different, to own a box to T is to own a T, it automatically drops T when it's dropped, and it always points to the heap.

one of the interesting parts is when you decouple these types from their behavior (I comprehend types as pairings of data and behavior), their all the same, their a usize integer that points to a byte. there is no fundamental difference to what usize*, &T, &mut T, and Box<T> store. the difference is all in compiler checks and behavior, the Drop trait for Box<T> tells the computer to run drop on T, where as the other two just drop themselves.

Wide Pointers

there is another important component to pointers, 'metadata', as best as I can tell a pointer is equivalent to (usize, T::metadata), metadata coming from the (unstable) Pointee trait, and it's what makes a pointer wide or thin. Pointee is defines metadata as a type other than unit (()) for three types, slices ([T]), str, and dyn Trait. slices store the number of elements as usize, str does bytes, and dyn Trait stores another pointer to it's vtable.

for slices and str this allows the program to know how long the array at the end is, so that you can iterate til the end, and for bounds checking, as well as how &[T] can be obtained from [T][{Range}] and know where it's bounds are, the pointer points to the range's lower bound-th element (or the first element if it's not lower bounded), and the upper bound is stored in the metadata as the difference from the first element in the borrow. I don't really want to get into what vtable does here though.

Points to where though?

this is FAR beyond the scope of my knowledge here, so maximum 'grain of salt' here. I envision three spaces a pointer points to, I consider them large chunks of contiguous, but largely ineffable memory.

the Stack where your local variables and execution is

the Heap where larger or unsized data goes

the Binary where you're functions, vtables, and string literals are stored (that's why string literals are &'static str) everything here is unwritable and it holds the actual 'program' part of your program

*as I get to later, wide pointers are a bit more than a usize

[abwwia]

helen-frankenthaler

Western Dream, 1957

Oil on unsized, unprimed canvas

70 × 86 in | 177.8 × 218.4 cm

[this-week-in-rust]

This Week in Rust 544

Hello and welcome to another issue of This Week in Rust! Rust is a programming language empowering everyone to build reliable and efficient software. This is a weekly summary of its progress and community. Want something mentioned? Tag us at @ThisWeekInRust on Twitter or @ThisWeekinRust on mastodon.social, or send us a pull request. Want to get involved? We love contributions.

This Week in Rust is openly developed on GitHub and archives can be viewed at this-week-in-rust.org. If you find any errors in this week's issue, please submit a PR.

Updates from Rust Community

Foundation

Guest Blog: Attending CISA’s Open Source Software Security Summit

Newsletters

This Month in Rust OSDev: March 2024

Project/Tooling Updates

lilos v1.0 released

medium-to-markdown v0.1.1 : Convert your medium blogs easily into markdown files

Fluvio v0.11.6 release and project updates

venndb 0.4.0 - custom validators

Tantivy 0.22: Performance improvements, new aggregations and stability fixes

Announcing r3bl_terminal_async - build async interactive CLIs in Rust

[video] Demo + architecture overview of Ferrostar, a cross-platform turn-by-turn navigation SDK with a Rust core

Observations/Thoughts

The Rust Calling Convention We Deserve

Sized, DynSized, and Unsized

Coroutines and effects

Porting a cross-platform GUI application to Rust

Adventures In Rust: Bringing Exchange Support To Thunderbird

Rust Walkthroughs

Why SQLite Performance Tuning made Bencher 1200x Faster

drop, the destructor of Rust structs

Building with AWS S3 using Rust

Rust tokio task cancellation patterns

[video] Build with Naz - Published crate r3bl_terminal_async for building async interactive CLIs in Rust

[video] Trent Billington - Bevy ECS - Power tool for data oriented applications

[video] Building a procedural art generator

[audio] Isograph with Robert Balicki

Research

A Study of Undefined Behavior Across Foreign Function Boundaries in Rust Libraries

Rust Digger: Does size matter? The biggest crate is 450MB; More than 100 crates are over 50MB

Miscellaneous

GitHub Sponsor Rust developer David Tolnay

Learn how to write TCP servers using Rust's std::net module

RustFest Zürich 🇨 Talks announced

Crate of the Week

This week's crate is scandir, a high-performance file tree scanner.

Thanks to Marty B. for the self-suggestion!

Please submit your suggestions and votes for next week!

Call for Testing

An important step for RFC implementation is for people to experiment with the implementation and give feedback, especially before stabilization. The following RFCs would benefit from user testing before moving forward:

No calls for testing were issued this week.

If you are a feature implementer and would like your RFC to appear on the above list, add the new call-for-testing label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature need testing.

Call for Participation; projects and speakers

CFP - Projects

Always wanted to contribute to open-source projects but did not know where to start? Every week we highlight some tasks from the Rust community for you to pick and get started!

Some of these tasks may also have mentors available, visit the task page for more information.

awesome-alternatives-in-rust - Add dqy alternative to dig

fluvio - When a topic is deleted, connected clients should have their connection closed

fluvio - MQTT Connector: Prefix auto generated Client ID to prevent connection drops

fluvio - Remove localhost from fluvio in favor of 127.0.0.1

If you are a Rust project owner and are looking for contributors, please submit tasks here.

CFP - Speakers

Are you a new or experienced speaker looking for a place to share something cool? This section highlights events that are being planned and are accepting submissions to join their event as a speaker.

RustConf 2024 | Closes 2024-04-25 | Montreal, Canada | Event date: 2024-09-10

RustLab 2024 | Closes 2024-05-01 | Florence, Italy | Event date: 2024-11-09 - 2024-11-11

EuroRust 2024| Closes 2024-06-03 | Vienna, Austria & online | Event date: 2024-10-10

Scientific Computing in Rust 2024| Closes 2024-06-14 | online | Event date: 2024-07-17 - 2024-07-19

Conf42 Rustlang 2024 | Closes 2024-07-22 | online | Event date: 2024-08-22

If you are an event organizer hoping to expand the reach of your event, please submit a link to the submission website through a PR to TWiR.

Updates from the Rust Project

432 pull requests were merged in the last week

add simple async drop glue generation

llvm backend: Prevent creating the same Instance::mono multiple times

static_mut_refs: use raw pointers to remove the remaining FIXME

add a lower bound check to unicode-table-generator output

add an opt-in to store incoming edges in VecGraph + misc

add llvm-bitcode-linker to build manifest

allow workproducts without object files

at debuginfo=0, don't inline debuginfo when inlining

correctly change type when adding adjustments on top of NeverToAny

coverage: branch coverage tests for lazy boolean operators

coverage: prepare for improved branch coverage

delay interning errors to after validation

delay span bug when Self kw resolves to DefKind::{Mod,Trait}

don't ICE for kind mismatches during error rendering

don't ascend into parent bodies when collecting stmts for possible return suggestion

don't error on subtyping of equal types

don't inline integer literals when they overflow - new attempt

don't repeatedly duplicate TAIT lifetimes for each subsequently nested TAIT

fix ICE in eval_body_using_ecx

fix ICE when there is a non-Unicode entry in the incremental crate directory

fix capturing duplicated lifetimes via parent in precise_captures (impl use<'...>)

fix normalizing in different ParamEnvs with the same InferCtxt

fix trait solver overflow with non_local_definitions lint

flip spans for precise capturing syntax not capturing a ty/const param, and for implicit captures of lifetime params

give a name to each distinct manipulation of pretty-printer FixupContext

ignore -C strip on MSVC

implement Modified Condition/Decision Coverage

implement PROBLEMATIC_CONSTS generalization

implement syntax for impl Trait to specify its captures explicitly (feature(precise_capturing))

improve ICE message for forbidden dep-graph reads

interpret: pass MemoryKind to adjust_alloc_base_pointer

interpret: pass MemoryKind to before_memory_deallocation

interpret: use ScalarInt for bin-ops; avoid PartialOrd for ScalarInt

introduce perma-unstable wasm-c-abi flag

let inherent associated types constrain opaque types during projection

make suggest_deref_closure_return more idiomatic/easier to understand

make thir_tree and thir_flat into hooks

make the comments for ReturnDest variants doc comments

match ergonomics 2024: Implement eat-one-layer

match ergonomics 2024: mut doesn't reset binding mode

match hyphen in multi-revision comment matchers

opaque types have no namespace

outline default query and hook provider function implementations

prefer identity equality over equating types during coercion

print note with closure signature on type mismatch

properly handle emojis as literal prefix in macros

remove default_hidden_visibility: false from wasm targets

remove uneeded clones now that TrustedStep implies Copy

silence some follow-up errors on trait impls in case the trait has conflicting or otherwise incoherent impls

simplify shallow resolver to just fold ty/consts

stop taking ParamTy/ParamConst/EarlyParamRegion/AliasTy by ref

subtype predicates only exist on inference types, so we can allow them to register opaque types within them

tell LLVM Vec::len is invariant across growth

use raw-dylib for Windows synchronization functions

refactor clippy in bootstrap

when suggesting RUST_BACKTRACE=1, add a special note for Miri's env var isolation

miri: data_race: make the release/acquire API more clear

miri: no_std works on Windows now

miri: add localtime_r shim

miri: address reuse improvements and fixes

miri: deadlock: show backtrace for all threads

miri: directly call handle_alloc_error

miri: implement support for __rust_alloc_error_handler

miri: make realloc with a size of zero fail

miri: move read_byte_slice to general helpers file, next to read_c_str

miri: threads: keep track of why we are blocked, and sanity-check that when waking up

Box::into_raw: make Miri understand that this is a box-to-raw cast

PatRangeBoundary::compare_with: also add a fast-path for signed integers

codegen ZSTs without an allocation

stabilize Wasm target features that are in phase 4 and 5

stabilize const_io_structs

stabilize checking of cfgs at compile-time: --check-cfg option

stabilize generic NonZero

make checked ops emit unchecked LLVM operations where feasible

improve std::fs::Metadata Debug representation

fix negating f16 and f128 constants

force exhaustion in iter::ArrayChunks::into_remainder

checked_ilog: improve performance

add an intrinsic for ptr::from_raw_parts(_mut)

fix: make str::from_raw_parts_mut mut

use queue-based RwLock on more platforms

add support for Arm64EC to the standard library

codegen_gcc: fix PassMode::Indirect with params

codegen_gcc: fix check for main function already declared

codegen_gcc: fix panic when calling get_fn for a variable

codegen_gcc: fix passing custom CG_RUSTFLAGS when building sysroot

codegen_gcc: implement more type kinds

cargo install: including Locking message

cargo resolver: add default Edition2024 to resolver v3

cargo resolver: add v3 resolver for MSRV-aware resolving

cargo credential: trim newlines in tokens from stdin

cargo msrv: error, rather than panic, on rust-version 'x'

cargo msrv: put MSRV-aware resolver behind a config

cargo toml: don't crash on parse errors that point to multi-byte character

cargo toml: disallow source-less dependencies

cargo toml: error on [project] in Edition 2024

cargo toml: report _fied variants (e.g. dev_dependencies) as deprecated

cargo: fix 'cargo build' fails when list_files() with gix is triggered

rustdoc: always display stability version even if it's the same as the containing item

rustdoc: fix copy path button

rustdoc: support type '/' to search

rustdoc-search: fix description on aliases in results

rustdoc-search: single result for items with multiple paths

clippy: threadlocal_initializer_can_be_made_const will not trigger for unreachable initializers

clippy: arithmetic_side_effects fix false negative on +=

clippy: ptr_as_ptr: fix duplicate diagnostics

clippy: emit the needless_pass_by_ref_mut lint on self arguments as well

clippy: fix is_test_module_or_function

clippy: reduce single_char_pattern to only lint on ascii chars

clippy: rework interior mutability detection

clippy: the multiple_unsafe_ops_per_block test needs asm!

rust-analyzer: cargo script mvp

rust-analyzer: add convert From to TryFrom assist

rust-analyzer: allow rust files to be used linkedProjects

rust-analyzer: VFS should not walk circular symlinks

rust-analyzer: handle escaped chars in doc comments

rust-analyzer: replace Just the variable name in Unused Variable Diagnostic Fix

rust-analyzer: implement BeginPanic handling in const eval

rust-analyzer: make test harness arguments configurable and not --nocapture

rust-analyzer: render matched macro arm on hover of macro calls

rust-analyzer: try to generate more meaningful names in json converter

Rust Compiler Performance Triage

A week dominated by small mixed changes to perf with improvements slightly outweighing regressions. There were no pure regressions, and many of the mixed perf results were deemed worth it for their potential improvements to runtime performance through further optimization from LLVM.

Triage done by @rylev. Revision range: ccfcd950..a77f76e2

Summary:

(instructions:u) mean range count Regressions ❌ (primary) 0.4% [0.2%, 1.8%] 57 Regressions ❌ (secondary) 0.4% [0.2%, 1.9%] 26 Improvements ✅ (primary) -0.8% [-3.4%, -0.2%] 50 Improvements ✅ (secondary) -0.6% [-1.9%, -0.1%] 32 All ❌✅ (primary) -0.2% [-3.4%, 1.8%] 107

0 Regressions, 5 Improvements, 6 Mixed; 2 of them in rollups 62 artifact comparisons made in total

Full report here

Call for Testing

An important step for RFC implementation is for people to experiment with the implementation and give feedback, especially before stabilization. The following RFCs would benefit from user testing before moving forward:

No calls for testing were issued this week.

RFCs

Rust

If you are a feature implementer and would like your RFC to appear on the above list, add the new call-for-testing label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature need testing.

Approved RFCs

Changes to Rust follow the Rust RFC (request for comments) process. These are the RFCs that were approved for implementation this week:

No RFCs were approved this week.

Final Comment Period

Every week, the team announces the 'final comment period' for RFCs and key PRs which are reaching a decision. Express your opinions now.

RFCs

[disposition: merge] experimental project goal program for 2024 H2

Tracking Issues & PRs

Rust

[disposition: merge] Tracking Issue for std::path::absolute

[disposition: merge] Tracking Issue for convenience methods on NonNull

[disposition: merge] Inline more svg images into CSS

[disposition: merge] Edition 2024: Make ! fall back to !

[disposition: merge] static_mut_refs: Should the lint cover hidden references?

Cargo

[disposition: merge] fix(toml): Warn, rather than fail publish, if a target is excluded

New and Updated RFCs

[new] experimental project goal program for 2024 H2

Upcoming Events

Rusty Events between 2024-04-24 - 2024-05-22 🦀

Virtual

2024-04-24 | Virtual + In Person (Prague, CZ) | Rust Czech Republic

#2: Making Safe Rust Safer (Pavel Šimerda)

2024-04-25 | Virtual (Berlin, DE) | OpenTechSchool Berlin + Rust Berlin

Rust Hack and Learn | Mirror: Rust Hack n Learn Meetup

2024-04-30 | Virtual (Dallas, TX, US) | Dallas Rust

Last Tuesday

2024-05-01 | Virtual (Cardiff, UK) | Rust and C++ Cardiff

Rust for Rustaceans Book Club: Chapter 5 - Project Structure

2024-05-01 | Virtual (Indianapolis, IN, US) | Indy Rust

Indy.rs - with Social Distancing

2024-05-02 | Virtual (Charlottesville, NC, US) | Charlottesville Rust Meetup

Crafting Interpreters in Rust Collaboratively

2024-05-07 | Virtual (Buffalo, NY) | Buffalo Rust Meetup

Buffalo Rust User Group

2024-05-09 | Virtual (Berlin, DE) | OpenTechSchool Berlin + Rust Berlin

Rust Hack and Learn | Mirror: Rust Hack n Learn Meetup

2024-05-09 | Virtual (Israel) | Rust in Israel

Rust at Microsoft, Tel Aviv - Are we embedded yet?

2024-05-09 | Virtual (Nuremberg/Nürnberg, DE) | Rust Nuremberg

Rust Nürnberg online

2024-05-14 | Virtual (Dallas, TX, US) | Dallas Rust

Second Tuesday

2024-05-14 | Virtual (Halifax, NS, CA) | Rust Halifax

Rust&Tell - Halifax

2024-05-14 | Virtual + In-Person (München/Munich, DE) | Rust Munich

Rust Munich 2024 / 1 - hybrid (Rescheduled)

2024-05-15 | Virtual (Vancouver, BC, CA) | Vancouver Rust

Rust Study/Hack/Hang-out

2024-05-16 | Virtual (Charlottesville, VA, US) | Charlottesville Rust Meetup

Crafting Interpreters in Rust Collaboratively

2024-05-21 | Virtual (Washington, DC, US) | Rust DC

Mid-month Rustful—forensic parsing via Artemis

Africa

2024-05-04 | Kampala, UG | Rust Circle Kampala

Rust Circle Meetup

Asia

2024-05-11 | Bangalore, IN | Rust Bangalore

May 2024 Rustacean meetup

Europe

2024-04-24 | Virtual + In Person (Prague, CZ) | Rust Czech Republic

#2: Making Safe Rust Safer (Pavel Šimerda)

2024-04-25 | Aarhus, DK | Rust Aarhus

Talk Night at MFT Energy

2024-04-25 | Berlin, DE | Rust Berlin

Rust and Tell - TBD

2024-04-25 | København/Copenhagen, DK | Copenhagen Rust Community

Rust meetup #46 sponsored by Nine A/S

2024-04-25 | Vienna, AT | Rust Vienna

Rust Vienna x Python User Group - April

2024-04-27 | Basel, CH | Rust Basel

Fullstack Rust - Workshop #2 (Register by 23 April)

2024-04-27 | Stockholm, SE | Stockholm Rust

Ferris' Fika Forum #2

2024-04-30 | Budapest, HU | Budapest Rust Meetup Group

Rust Meetup Budapest 2

2024-04-30 | Salzburg, AT | Rust Salzburg

[Rust Salzburg meetup]: 6:30pm - CCC Salzburg, 1. OG, ArgeKultur, Ulrike-Gschwandtner-Straße 5, 5020 Salzburg

2024-05-01 | Köln/Cologne, DE | Rust Cologne

This Month in Rust, May

2024-05-01 | Utrecht, NL | NL-RSE Community

NL-RSE RUST meetup

2024-05-06 | Delft, NL | GOSIM

GOSIM Europe 2024

2024-05-07 & 2024-05-08 | Delft, NL | RustNL

RustNL 2024

2024-05-08 | Cambridge, UK | Cambridge Rust Meetup

Monthly Rust Meetup

2024-05-09 | Gdańsk, PL | Rust Gdansk

Rust Gdansk Meetup #2

2024-05-14 | Virtual + In-Person (München/Munich, DE) | Rust Munich

Rust Munich 2024 / 1 - hybrid (Rescheduled)

2024-05-14 | Prague, CZ | Rust Prague

Rust Meetup Prague (May 2024)

2024-05-21 | Aarhus, DK | Rust Aarhus

Hack Night

2024-05-21 | Zurich, CH | Rust Zurich

Save the date - Mai Meetup

North America

2024-04-24 | Austin, TX, US | Rust ATX

Rust Lunch - Fareground

2024-04-25 | Nashville, TN, US | Music City Rust Developers

Music City Rust Developers - Async Rust on Embedded

2024-04-26 | Boston, MA, US | Boston Rust Meetup

North End Rust Lunch, Apr 26

2024-05-04 | Cambridge, MA, US | Boston Rust Meetup

Kendall Rust Lunch, May 4

2024-05-09 | Spokane, WA, US | Spokane Rust

Monthly Meetup: Topic TBD!

2024-05-12 | Brookline, MA, US | Boston Rust Meetup

Coolidge Corner Brookline Rust Lunch, May 12

2024-05-16 | Seattle, WA, US | Seattle Rust User Group

Seattle Rust User Group Meetup

2024-05-20 | Somerville, MA, US | Boston Rust Meetup

Ball Square Rust Lunch, May 20

2024-05-21 | San Francisco, CA, US | San Francisco Rust Study Group

Rust Hacking in Person

2024-05-22 | Austin, TX, US | Rust ATX

Rust Lunch - Fareground

Oceania

2024-04-30 | Auckland, NZ | Rust AKL

Rust AKL: Why Rust? Convince Me!

2024-04-30 | Canberra, ACT, AU | Canberra Rust User Group

CRUG April Meetup: Generics and Traits

If you are running a Rust event please add it to the calendar to get it mentioned here. Please remember to add a link to the event too. Email the Rust Community Team for access.

Jobs

Please see the latest Who's Hiring thread on r/rust

Quote of the Week

The learning curve for Rust is relatively steep compared to other languages, but once you climb it you'll never look down.

– BD103 on Mastodon

Thanks to BD103 for the self-suggestion!

Please submit quotes and vote for next week!

This Week in Rust is edited by: nellshamrell, llogiq, cdmistman, ericseppanen, extrawurst, andrewpollack, U007D, kolharsam, joelmarcey, mariannegoldin, bennyvasquez.

Email list hosting is sponsored by The Rust Foundation

Discuss on r/rust