一句话:提出静态开销语义与开销推断技术,为渐进类型程序推荐兼顾安全与性能的类型标注。
渐进类型允许静态与动态类型混用,但二者交互常导致难以预测的性能下降,阻碍用户添加类型标注。本文提出静态开销语义,准确预测渐进类型程序中静态-动态交互的开销;提出高效推断程序中所有可推断类型分配组合开销的技术;并将分析结果转化为具体建议与解释,帮助程序员理解、调试和优化性能。作者实现 Herder,对 Reticulated Python 程序的不同类型配置进行静态性能分析。在 15 个 Python 程序上的评估表明,Herder 能准确高效地推荐既优化性能又不牺牲静态类型安全保证的类型分配方案。
Gradual typing allows programmers to use both static and dynamic typing in a single program. However, a well-known problem with sound gradual typing is that the interactions between static and dynamic code can cause significant performance degradation. These performance pitfalls are hard to predict and resolve, and discourage users from using gradual typing features. For example, when migrating to a more statically typed program, often adding a type annotation will trigger a slowdown that can be resolved by adding more annotations elsewhere, but since it is not clear where the additional annotations must be added, the easier solution is to simply remove the annotation. To address these problems, we develop: (1) a static cost semantics that accurately predicts the overhead of static-dynamic interactions in a gradually typed program, (2) a technique for efficiently inferring such costs for all combinations of inferrable type assignments in a program, and (3) a method for translating the results of this analysis into specific recommendations and explanations that can help programmers understand, debug, and optimize the performance of gradually typed programs. We have implemented our approach in Herder, a tool for statically analyzing the performance of different typing configurations for Reticulated Python programs. An evaluation on 15 Python programs shows that Herder can use this analysis to accurately and efficiently recommend type assignments that optimize the performance of these programs without sacrificing the safety guarantees provided by static typing.
@article{paperbot286,
title = {Casts and costs: harmonizing safety and performance in gradual typing},
author = {John Peter Campora and Sheng Chen and Eric Walkingshaw},
journal = {Proceedings of the ACM on Programming Languages},
volume = {2},
number = {ICFP},
year = {2018},
doi = {10.1145/3236793}
}