Multiple Clippy `#[allow(...)]` in codebase

[Arjun31415]

There are multiple allow statements in the codebase -

1. Few in heap
   

   Rust/src/data_structures/heap.rs

   Lines 136 to 138 in fbc20a7

   	#[allow(clippy::new_ret_no_self)]
   	pub fn new<T>() -> Heap<T>
   	where

   
   

   Rust/src/data_structures/heap.rs

   Lines 148 to 150 in fbc20a7

   	#[allow(clippy::new_ret_no_self)]
   	pub fn new<T>() -> Heap<T>
   	where

2. In SHA256-

   Rust/src/ciphers/sha256.rs

   Lines 103 to 106 in fbc20a7

   	#[allow(dead_code)]
   	// Let's keep this utility function
   	pub fn get_hash_string(hash: &[u8; 32]) -> String {
   	let mut result = String::new();

3. In Salsa Cipher -
   

   Rust/src/ciphers/salsa.rs

   Lines 17 to 19 in fbc20a7

   	#[allow(dead_code)]
   	pub const C: [u32; 4] = [0x65787061, 0x6e642033, 0x322d6279, 0x7465206b];

4. In N-Queens-
   

   Rust/src/general/nqueens.rs

   Lines 1 to 5 in fbc20a7

   	#[allow(unused_imports)]
   	use std::env::args;
   	#[allow(dead_code)]
   	fn main() {

These are only few of them.
Should these be resolved or ignored ?

[siriak]

Done