A formalization of typed lua

Maidl, André Murbach; Mascarenhas, Fabio; Ierusalimschy, Roberto

doi:10.1145/2816707.2816709

Cited by 9 publications

(5 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Besides primitive and singleton types we have the dyn supertype for variables whose type cannot be properly inferred statically; function types, t → t; table types, { [ st ] : t ... } wkness, which include a tag (wkness) indicating the weakness of the table, and are restricted to be indexed by singleton types; recursive types, µy. t, to better support common programming idioms using tables; and product types, t × t and () (the empty tuple), which we use to express the domains of functions, though they have many other roles in typing Lua programs (see, for example, [17] express the domains of functions, though they have many other roles in typing Lua programs (see, for example, [17]).…”

Section: Type Systemmentioning

confidence: 99%

“…The first rule in Figure 17 shows the typing of a (non-weak) express the domains of functions, though they have many other roles in typing Lua programs (see, for example, [17]).…”

Section: Type Checkingmentioning

confidence: 99%

“…Our type inference algorithm follows the previously described process, with minor additions to tackle the problem of type inference given our subtyping relation, which is slightly more complex: we have the supertype dyn, tuple types and a slightly more complex subtyping relation for primitive types, since we also have singleton types. The main additions involve enriching the expressiveness express the domains of functions, though they have many other roles in typing Lua programs (see, for example, [17]).…”

Section: Type Inferencementioning

confidence: 99%

“…al. present Typed Lua [17], a type system for Lua 5.2 that tackles several of the complexities of the language, with special care in the typing of common idioms used by the community of Lua.…”

Section: Future and Related Workmentioning

confidence: 99%

See 3 more Smart Citations

Understanding Lua’s Garbage Collection

Soldevila

Ziliani

Fridlender³

2020

Proceedings of the 22nd International Symposium on Principles and Practice of Declarative Programming

View full text Add to dashboard Cite

We provide the semantics of garbage collection (GC) for the Lua programming language. Of interest are the inclusion of finalizers (akin to destructors in object-oriented languages) and weak tables (a particular implementation of weak references). The model expresses several aspects relevant to GC that are not covered in Lua's documentation but that, nevertheless, affect the observable behavior of programs. Our model is mechanized and can be tested with real programs. Our long-term goal is to provide a formalized static analyzer of Lua programs to detect potential dangers. As a first step, we provide a prototype tool, LuaSafe, that typechecks programs to ensure their behavior is not affected by GC. Our model of GC is validated in practice by the experimentation with its mechanization, and in theory by proving several soundness properties.

show abstract

Section: Type Systemmentioning

confidence: 99%

“…The first rule in Figure 17 shows the typing of a (non-weak) express the domains of functions, though they have many other roles in typing Lua programs (see, for example, [17]).…”

Section: Type Checkingmentioning

confidence: 99%

Section: Type Inferencementioning

confidence: 99%

Section: Future and Related Workmentioning

confidence: 99%

See 2 more Smart Citations

Understanding Lua’s Garbage Collection

Soldevila

Ziliani

Fridlender³

2020

Proceedings of the 22nd International Symposium on Principles and Practice of Declarative Programming

View full text Add to dashboard Cite

show abstract

“…IPS IMMA does not natively offer an export or import of data in a standard file type. In order to perform this export, IMMA offers a scripting language called Lua Scripting, through which the data of the models can be accessed through code [14]. Therefore, two codes in Lua Scripting were developed.…”

Section: Connecting the Platform To Production And Ergonomics Simulation Softwarementioning

confidence: 99%

Optimizing Ergonomics and Productivity by Connecting Digital Human Modeling and Production Flow Simulation Software

Pascual

Högberg

Syberfeldt

et al. 2020

Advances in Transdisciplinary Engineering

View full text Add to dashboard Cite

Simulation software is used in the production development process to simulate production and predict behaviors, calculate times, and plan production in advance. Digital human modeling (DHM) software is used to simulate humans working in production and assess whether workstation designs offer appropriate ergonomic conditions for the workers. However, these human simulations are usually carried out by human factors engineers or ergonomists, whereas the production simulations are carried out by production engineers. Lack of integration of these two simulations can lead to suboptimal solutions when the factory is not optimized to improve both productivity and ergonomics. To tackle this problem, a platform has been developed that connects production flow simulation software data and DHM software data and integrates them in a generic software for data treatment and visualization. Production flow simulation software data and DHM software data are organized in a hierarchical structure that allows synchronization between the production data and the ergonomic data on the target simulation software. The platform is generic and can be connected to any production flow simulation software and any DHM software by creating specific links for each software. The platform requires only the models of the production line, workstations, and tasks in order to perform the simulations in the target simulation software and collect the simulation results to present the results to the user of the platform.

show abstract

Type unsoundness in practice: an empirical study of Dart

Mezzetti

Møller

Strocco

2016

Proceedings of the 12th Symposium on Dynamic Languages

View full text Add to dashboard Cite

The type system in the Dart programming language is deliberately designed to be unsound: for a number of reasons, it may happen that a program encounters type errors at runtime although the static type checker reports no warnings. According to the language designers, this ensures a pragmatic balance between the ability to catch bugs statically and allowing a flexible programming style without burdening the programmer with a lot of spurious type warnings. In this work, we attempt to experimentally validate these design choices. Through an empirical evaluation based on open source programs written in Dart totaling 2.4 M LOC, we explore how alternative, more sound choices affect the type warnings being produced. Our results show that some, but not all, sources of unsoundness can be justified. In particular, we find that unsoundness caused by bivariant function subtyping and method overriding does not seem to help programmers. Such information may be useful when designing future versions of the language or entirely new languages.

show abstract

A formalization of typed lua

Cited by 9 publications

References 14 publications

Understanding Lua’s Garbage Collection

Understanding Lua’s Garbage Collection

Optimizing Ergonomics and Productivity by Connecting Digital Human Modeling and Production Flow Simulation Software

Type unsoundness in practice: an empirical study of Dart

Contact Info

Product

Resources

About