clear `xax` tests

Specialization of objects in EO programs.

Speco is a tool that is aimed to be launched on the EO program converted to a collection of .xmir files, which has undergone modifications performed by AOI tool.

Consider the following EO program:

[] > cat
  [] > talk
    QQ.io.stdout > @
      "Meow!"

[] > dog
  [] > talk
    QQ.io.stdout > @
      "Woof!"
  [] > eat
    QQ.io.stdout > @
      "I am eating"

[x] > pet1
  x.talk > @

[x] > pet2
  seq > @
    x.talk
    x.eat

The following block in the .xmir file of this program will be generated after AOI launch:

<aoi>
    <obj fqn="pet1.x">
       <inferred>
          <obj fqn="cat"/>
          <obj fqn="dog"/>
       </inferred>
    </obj>
    <obj fqn="pet2.x">
       <inferred>
          <obj fqn="dog"/>
       </inferred>
    </obj>
</aoi>

As we can see, object x from pet1 is only used with its talk attribute, therefore it can either be an instance of cat or dog. Whereas x located pet2 is used with both talk and eat, which lets us determine that x can only be an instance of dog.

Right now object pet1 has only one implementation, which looks like below in xmir format. It does not give any hints on what object x may be in this context.

<o abstract="" line="20" name="pet1" pos="0">
   <o line="20" name="x" pos="1"/>
   <o base="x" line="21" pos="2"/>
   <o base=".talk" line="21" name="@" pos="3"/>
</o>

Speco makes it obvious what x is in the provided context. For example, it will turn object pet1 into these two declarations of objects pet1_spec_x_cat and pet1_spec_x_dog, which are specific for cat and dog correspondingly.

<o abstract="" line="20" name="pet1_spec_x_cat" pos="0" spec="pet1">
   <o line="20" name="x" pos="1"/>
   <o base="x" line="21" pos="2"/>
   <o base=".talk" line="21" name="@" pos="3"/>
</o>

<o abstract="" line="20" name="pet1_spec_x_dog" pos="0" spec="pet1">
   <o line="20" name="x" pos="1"/>
   <o base="x" line="21" pos="2"/>
   <o base=".talk" line="21" name="@" pos="3"/>
</o>

It will generate a collection of modified .xmir files as an output.

Usage

Build the app locally:

$ make build

and run:

$ java -jar speco.jar --help

To run a transformation:

$ java -jar speco.jar --source=<input> --target=<output>

or use make command:

$ make trans

How it works

The tool works according to an algorithm consisting of 7 transformation rules.

Rule 1:

Create a <speco/> node consisting of specialized <versions/> nodes for all objects inferred by AOI;
Each node has attributes:
- @name -- name of the polymorphic object,
- @var -- name of the polymorphic attribute of this object,
- @spec -- name of the object that specializes this attribute;
Each node consists of a single object copied from the <objects/> node by name @name, but also changed attributes:
- @name replaced by @name_spec_@var_@spec
- @spec equal version@spec
Copy all specialized objects (content of the <version/> node) to the <objects/> node.

Rule 2:

For all applications: if there is a polymorphic base object and a specialized version is uniquely determined, then a replacement to determined version occurs.

Rule 3:

For each object, for each of its specialized/polymorphic versions, create a with-* attribute that would returns a new object for the current version. The current state of the object should be deeply copied into the new object.

Rule 4:

Search for all fence attributes, that reference to the memory wrapper object;
Create copies of these attributes, modifying them so that tuple with the object it returned before and the "parent" object is returned.

Rule 5:

Replace accessing the "parent" object with creating an intermediate tuple object and getting its first element.

Rule 6:

Replace calls of the "parent" object (all except the first one) with calls of the second elements of intermediate tuples in the order in the program. Later this should be replaced by using EOG.

Rule 7:

Modify the *-as-tuple attribute so that it returns a new object instead of changing itself by using the with-* attribute.

How to Contribute

Fork repository, make changes, send us a pull request. We will review your changes and apply them to the master branch shortly, provided they don't violate our quality standards. To avoid frustration, before sending us your pull request please run full Maven build:

$ mvn clean install -Pqulice

You will need Maven 3.3+ and Java 8+.

	* @todo #32:30min investigate problem with @DisableOnOs(OS.Windows),
	* this is an issue of junit -- https://github.com/junit-team/junit5/issues/2811,
	* maybe try to manually delete each created file or use a pat
	* or get rid of the @TempDir.

	@todo #47:30min add unit-test for transformation,
	in which the input will be xmir with applications with polymorphic objects and
	the expected result will be the same xmir with an applications with their
	specialized versions.

	@todo #47:30min add unit-test for transformation,
	in which the input will be xmir without a <speco/> section and
	the expected result will be the same xmir with a <speco/> section
	duplicating <aoi/>.

	@todo #47:30min add unit-test for transformation,
	in which the input will be xmir with a <speco/> section duplicating <aoi/> and
	in the expected result will be the same xmir with a specialized objects
	in the <speco/> section.

	@todo #68:30min add unit-test for transformation,
	in which the input will be xmir with object with fence attribute,
	the expected result will be the same xmir with a *-as-tuple attribute
	for this fence attribute.

	* @todo #63:30min enable convertsFromEO test:
	* we need to remove @disable annotation for these test
	* when we provide the rule 3 implementation and add an appropriate transformation.

	* @todo #39:60min refactor this interface and classes EoWalk and XmirWalk implementing it,
	* to avoid code duplication. In particular, in the fields (input, output and speco),
	* constructor and exec method.

	* @todo #22:90min add separate unit-test for each transformation,
	* which would run step by step and check the intermediate results,
	* for example, use yml packs as in dejump.

	* @todo #63:30min enable convertsFromXmir test:
	* we need to remove @disable annotation for these test
	* when we provide the rule 3 implementation and add an appropriate transformation.

	@todo #64:30min add unit-test for transformation,
	in which the input will be xmir with polymorphic object and
	the expected result will be the same xmir with a with-* attributes
	for all specialized versions of this polymorphic object.

	@todo #47:30min add unit-test for transformation,
	in which the input will be xmir with a specialized objects in <speco/> section and
	the expected result will be the same xmir with a specialized object in <objects/> section.

objectionary / speco Goto Github PK

speco's Introduction

Usage

How it works

How to Contribute

speco's People

Contributors

Stargazers

Watchers

Forkers

speco's Issues

Rate-Limited

Open

Detected dependencies

Recommend Projects

Recommend Topics

Recommend Org