103 Commits

Author	SHA1	Message	Date
Michael Gottesman	b0522635d4	[silgen] Instead of computing the indirect result addrs as we build/store it. Just generate it dynamically. ... This is being done in preparation for moving ResultPlan /out of/ SILGenFunction::apply. rdar://30955427	2017-03-14 00:39:48 -07:00
Michael Gottesman	6769f78460	[silgen] Standardize field names in ResultPlan.{cpp,h} to match SILGen norms of camelCase instead of CamelCase.	2017-03-13 19:29:05 -07:00
Michael Gottesman	8521601215	[silgen] Move ResultPlan from SILGenApply.cpp -> ResultPlan.{h,cpp} ... ResultPlan and related constructs have already been written in a type erased fashion. This commit takes advantage of this by moving the details of the code to ResultPlan.{cpp,h}. This slims down SILGenApply.cpp in a NFC way and ensures that other code in SILGenApply can not depend on the details of ResultPlan. Also it is my hope that this can become the beginning of the merging of the ResultPlan from SILGenApply and from SILGenPoly. We should only have 1 way in SILGen to build applies and create apply results. rdar://29791263	2017-03-13 10:32:33 -07:00