19:14:01galdorSEARCH works but MISMATCH will stop at the first element which fails the comparison so it's better
19:14:51Shinmerawell search would also abort early since they couldn't match anyway due to the two sub regions not being long enough anymore for a match anyway.
19:15:09Shinmerabut SEARCH does not convey the intention very well.
19:26:35phoeoh look, this function exists in the standard
19:26:48phoeI remember that I learned about its existence then forgot about it again like three times now
19:27:42phoetime to forget about it for the fourth time
19:28:49BirthdayboiJoshI was just skimming over ANSI Common Lisp and saw mismatch, I didn't know it existed, and then this conversation happened 2 minutes after
19:29:10travv0it's pretty embarrassing how often i forget and am reminded of even commonly used functions
19:29:22BirthdayboiJoshWell there are a huge amount of them :D
2:50:51saraviaphoe, sorry but .net core is the same of C#, becose Lovesan/bike tell me ".net core and c++" but i need interoperate -> C# Frameworks 4, is posible doc?
2:52:06saraviabut this work names "interoperate" no?
2:53:18saraviamy new job requires visual studio, but to me is more inspiration "interoperate with common lisp + portacle (Emacs) xD"
2:53:47pjbsaravia: AFAIK, there is no CL compiler targetting .Net. Instead, you can write the core of your application in Common Lisp, running in a separate process, and communicating with the .Net environment thru socketsr.