Summary

CR: enable "scrutiny" be default

Metadata

• Id: 66794cd896ef95837e9de107e7877c7ad64589c8
• Trac id: 932
• Type: enhancement
• Reporter: felix
• Owner:
• Cc:
• Status: closed
• Component: compiler
• Estimated difficulty:
• Resolution: fixed
• Priority: minor
• Milestone: someday
• Version: 4.8.x
• Changetime: 2012-10-27 17:21:37 UTC
• Created: 2012-10-08 20:23:58 UTC
• Keywords:

Description

Flow- and type-analysis only enabled with the `-scrutinize` or `-specialize` options, or when an optimization-level > 2 is selected. Since the type-analysis can catch many errors, sjamaan suggested to enable scrutiny by default (note that this doesn't automatically imply specialization, i.e. optimizations based on the analysis).

To avoid incorrect warnings in code that redefines standard bindings, scrutiny should be disabled when the `-no-usual-integrations` option (implied by optimization level 0) is given.

Changes and comments

[2012-10-15 11:28:55 UTC] felix wrote:

scrutiny by default?; Yes; No)]

[2012-10-15 16:42:16 UTC] johnwcowan wrote:

Replying to felix: > scrutiny by default?; Yes; No)]

[2012-10-24 09:26:19 UTC] felix changed type from change request to enhancement

[2012-10-24 09:26:19 UTC] felix wrote:

Accepted.

[2012-10-27 17:21:37 UTC] felix changed status from new to closed

[2012-10-27 17:21:37 UTC] felix set resolution to fixed