well, separate function is not required when it comes to triggering lifetime-related compiler errors

Author: vthriller

src/nla.rs

@@ -375,15 +375,6 @@ mod tests {
         assert_eq!(nla_align!(get_len() - 3), usize::MAX);
     }
 
-    // compile-time test: it should be possible to pass &[u8] through
-    // NlasIterator and return one of its output &[u8]s without facing
-    // compiler error about lifetimes and returning borrows from something
-    // that this funciton owns
-    fn last_nla_from_buffer(nlas: &[u8]) -> Option<Result<&[u8], DecodeError>> {
-        NlasIterator::new(nlas).last()
-            .map(|nla| nla.map(|nla| nla.value()))
-    }
-
     #[test]
     fn test_nlas_iterator() {
         // sample NFTA_LIST_ELEM from nftables, with nested nlas at the end
@@ -404,6 +395,16 @@ mod tests {
 
         // this sholud be an Err()
         let truncated = &NESTED_NLAS[ .. NESTED_NLAS.len()-1];
-        assert!(last_nla_from_buffer(truncated).unwrap().is_err());
+        assert!(NlasIterator::new(truncated).last().unwrap().is_err());
+
+        let last = {
+            // it should be possible to pass &[u8] through
+            // NlasIterator and return one of its output &[u8]s without facing
+            // compiler error about lifetimes and returning borrows from
+            // something is limited to this scope
+            let last = NlasIterator::new(NESTED_NLAS).last();
+            last.unwrap().unwrap().value()
+        };
+        assert_eq!(last, &NESTED_NLAS[16..]);
     }
 }