After the last update, some of my html views generated errors. The problem is that it is a very used piece of code which was correct until last update.

An example:

if(recid != null && Contacts[ID == recid.tolong()].count() > 0)

{

// some piece of code

} 

Iff recid is null, the code Contacts[ID == recid.tolong()].count() was no more executed . This was the behavior before the last update and it was convenient. The condition checks if the record is null and ONLY if it is not null it checks if there is a record with the ID value of the recid.tolong()  . It makes sense, because it is a waste of time for the compiler to check the second condition when it is obvious that if condition will not be meet, because there is && operator and one of the statements is false. 

Actually, even if the condition recid != null is false, Contacts[ID == recid.tolong()].count() > 0 is checked as well, and it gives an error because recid is null and can't be converted to number. 

The problem is that this is a quite common piece of code - if you made many applications it is not quite simple to check them all for a records count in an if statement... so it was inevitable to receive several complains and some other probably will follow. 

If possible, restore the old behaviour, which had nothing wrong in it and will save compiler from making additional unuseful checks.