From 7ad85fca6d0ce5a8e62be67de7ec3d396670ca74 Mon Sep 17 00:00:00 2001
From: lucasart <lucas.braesch@gmail.com>
Date: Tue, 25 Aug 2015 19:46:37 +0800
Subject: [PATCH] Prune castling moves

Align the behaviour with reductions. Initially castling moves had to be
treated differently, because the SEE did not handle them correctly. But now it
does.

STC:
LLR: 2.96 (-2.94,2.94) [-3.00,1.00]
Total: 83750 W: 15722 L: 15711 D: 52317

LTC:
LLR: 2.95 (-2.94,2.94) [-3.00,1.00]
Total: 97183 W: 15120 L: 15115 D: 66948

bench 7759837

Resolves #403
---
 src/search.cpp | 1 -
 1 file changed, 1 deletion(-)

diff --git a/src/search.cpp b/src/search.cpp
index 17b93ce7..d8101e55 100644
--- a/src/search.cpp
+++ b/src/search.cpp
@@ -880,7 +880,6 @@ moves_loop: // When in check and at SpNode search starts from here
           && !captureOrPromotion
           && !inCheck
           && !givesCheck
-          &&  type_of(move) == NORMAL
           && !pos.advanced_pawn_push(move)
           &&  bestValue > VALUE_MATED_IN_MAX_PLY)
       {
-- 
2.39.2