Clippy complex type warning

rust/nasl-builtin-utils/src/context.rs

@@ -5,7 +5,7 @@
 //! Defines the context used within the interpreter and utilized by the builtin functions
 
 use nasl_syntax::{logger::NaslLogger, Loader, NaslValue, Statement};
-use storage::{types::Primitive, Dispatcher, Field, Kb, Retriever};
+use storage::{Dispatcher, Retriever};
 
 use crate::lookup_keys::FC_ANON_ARGS;
 
@@ -283,7 +283,6 @@ impl Default for Register {
 }
 use std::{
     collections::HashMap,
-    time::{SystemTime, UNIX_EPOCH},
 };
 type Named = HashMap<String, ContextType>;
 

rust/nasl-interpreter/src/fork_interpreter.rs

@@ -5,13 +5,15 @@ use nasl_syntax::Statement;
 
 use crate::interpreter::InterpretResult;
 
+/// To allow closures we use a heap stored statement consumer
+pub type StatementConsumer = Box<dyn Fn(&Statement)>;
 /// Uses given code to return results based on that.
 pub struct CodeInterpreter<'a, 'b, K> {
     lexer: nasl_syntax::Lexer<'b>,
     interpreter: crate::interpreter::Interpreter<'a, K>,
     statement: Option<Statement>,
     /// call back function for Statements before they get interpret
-    pub statemet_cb: Option<Box<dyn Fn(&Statement)>>,
+    pub statemet_cb: Option<StatementConsumer>,
 }
 
 impl<'a, 'b, K> CodeInterpreter<'a, 'b, K>

rust/storage/src/retrieve.rs

@@ -85,6 +85,8 @@ impl Retrieve {
 }
 
 /// Retrieves fields based on a key and scope.
+// TODO: remove K infavor of a enum, as a user of that interface it is very hard to differentiate
+// when to use an OID and when not. A better solution would be to use enums.
 pub trait Retriever<K> {
     /// Gets Fields find by key and scope. This is to get all instances.
     fn retrieve(
@@ -94,6 +96,8 @@ pub trait Retriever<K> {
     ) -> Result<Box<dyn Iterator<Item = Field>>, StorageError>;
 
     /// Gets Fields find by field and scope.
+    ///
+    /// This is used to filter results.
     fn retrieve_by_field(
         &self,
         field: Field,