From 2d6fedbf7f8ab21190a8f33a93e350756b813ec2 Mon Sep 17 00:00:00 2001
From: HuskyHacks <57866415+HuskyHacks@users.noreply.github.com>
Date: Wed, 30 Mar 2022 13:46:42 -0400
Subject: [PATCH] removing unneeded to_string()

---
 Litcrypt_String_Encryption/src/main.rs | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Litcrypt_String_Encryption/src/main.rs b/Litcrypt_String_Encryption/src/main.rs
index 4c9eed2..3bce718 100644
--- a/Litcrypt_String_Encryption/src/main.rs
+++ b/Litcrypt_String_Encryption/src/main.rs
@@ -10,7 +10,7 @@ fn main(){
     let evil_password: String = "OhNoPayUsBitcoin!@#".to_string();
 
     // If I want to encrypt a literal string, I can use the lc!() macro. This and the use_litcrypt() method will encrypt anything that is passed as the argument.
-    let _can_you_see_me: String = lc!("Can you see me?").to_string();
+    let _can_you_see_me: String = lc!("Can you see me?");
     // You will not see the above string in the bin once it is compiled. You WILL see this one, because we aren't using the lc!() macro:
     let _or_can_you_see_me: String = "Or can you see me?".to_string();
 
@@ -42,4 +42,4 @@ fn main(){
 
     // fn solemly_swear_up_to_no_good() { ......
 
-    // ... and all of the strings of these functions can use litcrypt to evade static analyzers.
\ No newline at end of file
+    // ... and all of the strings of these functions can use litcrypt to evade static analyzers.