summaryrefslogtreecommitdiff
path: root/solutions/16_lifetimes/lifetimes1.rs
diff options
context:
space:
mode:
authormo8it <mo8it@proton.me>2024-07-05 13:39:50 +0200
committermo8it <mo8it@proton.me>2024-07-05 13:39:50 +0200
commit7123c7ae3a9605fbe962e4ef0a0f1424cd16fef8 (patch)
treec67f7e62bb9a179ae4fdbab492501cb6847e64c7 /solutions/16_lifetimes/lifetimes1.rs
parent77b687d501771c24bd83294d97b8e6f9ffa92d6b (diff)
parent4d9c346a173bb722b929f3ea3c00f84954483e24 (diff)
Merge remote-tracking branch 'upstream/main' into fix-enum-variant-inconsistency
Diffstat (limited to 'solutions/16_lifetimes/lifetimes1.rs')
-rw-r--r--solutions/16_lifetimes/lifetimes1.rs28
1 files changed, 28 insertions, 0 deletions
diff --git a/solutions/16_lifetimes/lifetimes1.rs b/solutions/16_lifetimes/lifetimes1.rs
new file mode 100644
index 0000000..ca7b688
--- /dev/null
+++ b/solutions/16_lifetimes/lifetimes1.rs
@@ -0,0 +1,28 @@
+// The Rust compiler needs to know how to check whether supplied references are
+// valid, so that it can let the programmer know if a reference is at risk of
+// going out of scope before it is used. Remember, references are borrows and do
+// not own their own data. What if their owner goes out of scope?
+
+fn longest<'a>(x: &'a str, y: &'a str) -> &'a str {
+ // ^^^^ ^^ ^^ ^^
+ if x.len() > y.len() {
+ x
+ } else {
+ y
+ }
+}
+
+fn main() {
+ // You can optionally experiment here.
+}
+
+#[cfg(test)]
+mod tests {
+ use super::*;
+
+ #[test]
+ fn test_longest() {
+ assert_eq!(longest("abcd", "123"), "abcd");
+ assert_eq!(longest("abc", "1234"), "1234");
+ }
+}