Frontend: Remove no-op -stress-astscope-lookup flag

This commit is contained in:
Slava Pestov
2020-09-22 14:41:58 -04:00
parent f718a4cdd2
commit 4bbdb95f4f
3 changed files with 0 additions and 7 deletions

View File

@@ -251,9 +251,6 @@ namespace swift {
/// Someday, ASTScopeLookup will supplant lookup in the parser
bool DisableParserLookup = false;
/// Should we stress ASTScope-based resolution for debugging?
bool StressASTScopeLookup = false;
/// Whether to enable the new operator decl and precedencegroup lookup
/// behavior. This is a staging flag, and will be removed in the future.
bool EnableNewOperatorLookup = false;

View File

@@ -157,9 +157,6 @@ def disable_target_os_checking :
def crosscheck_unqualified_lookup : Flag<["-"], "crosscheck-unqualified-lookup">,
HelpText<"Compare legacy DeclContext- to ASTScope-based unqualified name lookup (for debugging)">;
def stress_astscope_lookup : Flag<["-"], "stress-astscope-lookup">,
HelpText<"Stress ASTScope-based unqualified name lookup (for testing)">;
def use_clang_function_types : Flag<["-"], "use-clang-function-types">,
HelpText<"Use stored Clang function types for computing canonical types.">;

View File

@@ -426,7 +426,6 @@ static bool ParseLangArgs(LangOptions &Opts, ArgList &Args,
}
Opts.DisableParserLookup |= Args.hasArg(OPT_disable_parser_lookup);
Opts.StressASTScopeLookup |= Args.hasArg(OPT_stress_astscope_lookup);
Opts.EnableNewOperatorLookup = Args.hasFlag(OPT_enable_new_operator_lookup,
OPT_disable_new_operator_lookup,
/*default*/ false);