I love it when the photo of a component and the schematic drawing on the data sheet disagree with each other.
(e.g.: digikey.ca/en/products/detail/…)
Guess I'll have to wait 'till I have the physical component in my possession to find out for sure.
Ep. 311 Ant Hill Kids PATREON Episode Part 2
In this Patreon deep-dive from the vault, I look into the Ant Hill Kids, truly one of the worst cults I have ever researched or heard about to this day. This isSpreaker
For all the filtering options that DigiKey has on their web site, I wish you could filter based on minimum order quantity.
No, I do not want to buy 3000 voltage regulators.
When a bear attacks you, you generally die and then it's over. When a man attacks, you live with that trauma for life.
like this
The great thing about being an adult is that if you want to have candy for dinner, nobody is going to stop you.
The terrible thing about being an adult is that if you want to have candy for dinner, nobody is going to stop you.
𝚛𝚊𝚝 reshared this.
Maintenance and Release Schedule
☁️ Nextcloud server, a safe home for all your data - nextcloud/serverGitHub
@Björn Schießle I think I figured out my problem. I'm running an older version of PHP that is no longer supported by later versions.
Edit: It irks me that it didn't warn me about this before now though.
Something that's been bothering me about lifetimes.
When I got to this section in the book, I couldn't (and still can't) understand why it's necessary to specify lifetimes for the references a struct holds. I mean, if I have:
struct Foo<'a> {
bar: &'a String,
}Shouldn't it just be assumed that the data referenced by Foo::bar should have to live at least as long as the Foo object itself? Why does this have to be explicitly stated? Is there some scenario where you would want this to not be the case?
Edit: formatting fix
Adam Hunt likes this.
Lifetime elision only applies on function signatures. It might be because no one has done the work? Though I think it's nice to be explicit that the struct holds a reference to something.
Explicit lifetimes would be necessary for a struct with multiple references (or I guess a rule that says they're either all the same or all unique). These are not the same:
struct Foo<'a> {
bar: &'a String,
baz: &'a String,
}
struct Foo<'a, 'b> {
bar: &'a String,
baz: &'b String,
}More info on the elision rules is at the Rustonomicon.
Lifetime Elision - The Rustonomicon
The Dark Arts of Advanced and Unsafe Rust Programmingdoc.rust-lang.org
Jonathan Lamothe likes this.
&self and return a reference.
Ep. 311 Ant Hill Kids PATREON Episode Part 1
In this Patreon deep-dive from the vault, I look into the Ant Hill Kids, truly one of the worst cults I have ever researched or heard about to this day. This isSpreaker
Ep. 310 Physically In, Mentally Out - Episode 116 Remastered
In this episode I chat with author Geoffrey Wallis about his book "A Voice From Inside - Notes on Religious Trauma In a Captive Organization".Spreaker
Ep. 309 The Covenant, the Sword and the Arm of the Lord Part 2 - Episode 107 Remastered
In this remastered conversation, I speak with former co-leader of the Covenant, the Sword and the Arm of the Lord (CSA). Unfortunately, I found out recently that Kerry passed away last year.Spreaker
Ep. 309 The Covenant, the Sword and the Arm of the Lord Part 1 - Episode 107 Remastered
In this remastered conversation, I speak with former co-leader of the Covenant, the Sword and the Arm of the Lord (CSA). Unfortunately, I found out recently that Kerry passed away last year.Spreaker
Jonathan Lamothe
in reply to Jonathan Lamothe • •