Issue 250553004: Always treat [call] members as closures during tracing.

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 250553004: Always treat [call] members as closures during tracing. (Closed)

Created:
6 years, 8 months ago by herhut

Modified:
6 years, 8 months ago

Reviewers:
sra1

CC:
reviews_dartlang.org, floitsch

Base URL:
https://dart.googlecode.com/svn/branches/bleeding_edge/dart

Visibility:
Public.

Created: 6 years, 8 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+22 lines, -10 lines)			Patch
	M	sdk/lib/_internal/compiler/implementation/inferrer/node_tracer.dart	View		1 chunk	+9 lines, -0 lines	0 comments	Download
	A +	tests/compiler/dart2js_extra/18383_test.dart	View		1 chunk	+13 lines, -10 lines	0 comments	Download

Total messages: 3 (0 generated)

herhut

Properly handling [call] is on my list of things to do but that might take ...

6 years, 8 months ago (2014-04-24 13:15:03 UTC) #1

herhut

6 years, 8 months ago (2014-04-25 06:50:34 UTC) #3

Message was sent while issue was closed.

Committed patchset #1 manually as r35417 (presubmit successful).