glitch.land

Recent Posts

A byte-sized unique identifier Printing In Virtual Reality Emulating CHIP-8

Impressive Claude Code Features

I’ve been spending some time exploring Claude Code at work, and a few features stood out to me, so I wanted to share. …

March 30, 2026 • 5 min read •

LLM Self Confidence

Before I begin, I must disclose my expertise is in software engineering, game dev, and application security. I have a …

June 27, 2025 • 23 min read •

OSX Keychain For CLI Secrets

Using macos keychain to store and retrieve secrets from bash scripts

January 12, 2024 • 7 min read •

1 2 3 4 5 6 7 8 Next

MICRO - FEED

2026-02-13 11:46:27 Rust Non-Lexical Lifetimes

Sorry for lack of content, I’m still alive, life has just been very hard. I will try to get back to writing more ❤️.

I was doing a quiz on rust lifetimes last night, and got the following question wrong. Will this code compile?

let mut v = vec![1, 2, 3];
let a = &v[0];
println!("{a}");
v.push(4);

Click here to see the answer :)

I thought it would not compile, because a takes read ownership, and push needs read + write access. But I was wrong!

It does compile! It’s due to a Rust feature called Non-Lexical Lifetimes (added in 2018). So along with the other rules, the borrow checker also asks: “Is there any path where the borrow is used after this point?” If the answer is no, the borrow ends there!

  let mut v = vec![1, 2, 3];
  let a = &v[0];      // immutable borrow starts
  println!("{a}");    // last use of `a` - borrow ENDS here with NLL
  v.push(4);          // RW mutable borrow is fine, no conflict

I hope this helps others learning Rust (its a beautiful language)

2025-06-24 11:30:18 Micros

Even when I’m super busy :D

View All Micros