Issue 2829683008: Use a non-null TypeInferrer even in non-strong mode.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Issue 2829683008: Use a non-null TypeInferrer even in non-strong mode. (Closed)

Created:
3 years, 8 months ago by Paul Berry

Modified:
3 years, 8 months ago

Reviewers:
ahe

CC:
reviews_dartlang.org, dart-fe-team+reviews_google.com

Target Ref:
refs/heads/master

Visibility:
Public.

Use a non-null TypeInferrer even in non-strong mode. This is necessary because some of the TypeInferrer's roles (e.g. type promotion and determination of the types of constants) are still needed in non-strong mode. R=ahe@google.com Committed: https://github.com/dart-lang/sdk/commit/e3347e03f70b5e276216c63ddaf8e1d8127301ae

Created: 3 years, 8 months ago

Download [raw] [tar.bz2]

	Unified diffs	Side-by-side diffs	Stats (+10 lines, -8 lines)			Patch
M	pkg/front_end/lib/src/fasta/kernel/body_builder.dart	View	1 chunk	+1 line, -1 line	0 comments	Download
M	pkg/front_end/lib/src/fasta/kernel/kernel_shadow_ast.dart	View	1 chunk	+2 lines, -2 lines	0 comments	Download
M	pkg/front_end/lib/src/fasta/source/source_loader.dart	View	1 chunk	+2 lines, -3 lines	0 comments	Download
M	pkg/front_end/lib/src/fasta/type_inference/type_inferrer.dart	View	2 chunks	+5 lines, -2 lines	0 comments	Download

Total messages: 5 (2 generated)

Paul Berry

3 years, 8 months ago (2017-04-20 11:11:25 UTC) #5

Message was sent while issue was closed.

Committed patchset #1 (id:1) manually as
e3347e03f70b5e276216c63ddaf8e1d8127301ae (presubmit successful).