From 47543e5df11bb4e7e9f7b653c65cee54d957b307 Mon Sep 17 00:00:00 2001
From: aaron <aaronweiss@roblox.com>
Date: Tue, 5 Nov 2024 15:25:38 -0800
Subject: [PATCH] Set the defining module even when the new solver cloned the
 type. (#1506)

Follow up to #1495: a small fixup for the defining module and location
to get set even when cloning was required.
---
 Analysis/src/ConstraintSolver.cpp | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/Analysis/src/ConstraintSolver.cpp b/Analysis/src/ConstraintSolver.cpp
index bcda4e23..398f0aa5 100644
--- a/Analysis/src/ConstraintSolver.cpp
+++ b/Analysis/src/ConstraintSolver.cpp
@@ -1109,7 +1109,8 @@ bool ConstraintSolver::tryDispatch(const TypeAliasExpansionConstraint& c, NotNul
 
             target = follow(instantiated);
         }
-        else if (FFlag::LuauNewSolverPopulateTableLocations)
+
+        if (FFlag::LuauNewSolverPopulateTableLocations)
         {
             // This is a new type - redefine the location.
             ttv->definitionLocation = constraint->location;