Changeset 0536c03 for src/ResolvExpr/CandidateFinder.cpp
- Timestamp:
- Dec 23, 2020, 4:45:08 PM (4 years ago)
- Branches:
- ADT, arm-eh, ast-experimental, enum, forall-pointer-decay, jacob/cs343-translation, master, new-ast-unique-expr, pthread-emulation, qualifiedEnum
- Children:
- 09867ec
- Parents:
- bd144fd
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
src/ResolvExpr/CandidateFinder.cpp
rbd144fd r0536c03 905 905 // xxx - is it possible that handleTupleAssignment and main finder both produce candidates? 906 906 // this means there exists ctor/assign functions with a tuple as first parameter. 907 funcFinder.find( untypedExpr->func, selfFinder.candidates.empty() ? ResolvMode::withAdjustment() : ResolvMode::withoutFailFast() ); 907 ResolvMode mode = { 908 true, // adjust 909 !untypedExpr->func.as<ast::NameExpr>(), // prune if not calling by name 910 selfFinder.candidates.empty() // failfast if other options are not found 911 }; 912 funcFinder.find( untypedExpr->func, mode ); 908 913 // short-circuit if no candidates 909 914 // if ( funcFinder.candidates.empty() ) return;
Note: See TracChangeset
for help on using the changeset viewer.