NCGenerics: back-out @NoEscape being ~Escapable

I thought this would be simple to add a check for this, but it turns out
that a more complete refactoring that eliminates `isNoEscape` in favor
of `isEscapable` is most likely needed.

Author: kavon

lib/AST/ConformanceLookup.cpp

@@ -274,14 +274,21 @@ static bool isSendableFunctionType(EitherFunctionType eitherFnTy) {
 
 /// Whether the given function type conforms to Escapable.
 static bool isEscapableFunctionType(EitherFunctionType eitherFnTy) {
-  if (auto silFnTy = eitherFnTy.dyn_cast<const SILFunctionType *>()) {
-    return !silFnTy->isNoEscape();
-  }
-
-  auto functionType = eitherFnTy.get<const FunctionType *>();
+//  if (auto silFnTy = eitherFnTy.dyn_cast<const SILFunctionType *>()) {
+//    return !silFnTy->isNoEscape();
+//  }
+//
+//  auto functionType = eitherFnTy.get<const FunctionType *>();
+//
+//  // TODO: what about autoclosures?
+//  return !functionType->isNoEscape();
 
-  // TODO: what about autoclosures?
-  return !functionType->isNoEscape();
+  // FIXME: unify TypeBase::isNoEscape with TypeBase::isEscapable
+  // LazyConformanceEmitter::visitDestroyValueInst chokes on these instructions
+  // destroy_value %2 : $@convention(block) @noescape () -> ()
+  //
+  // Wrongly claim that all functions today conform to Escapable for now:
+  return true;
 }
 
 static bool isBitwiseCopyableFunctionType(EitherFunctionType eitherFnTy) {