You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Radu Cotescu (JIRA)" <ji...@apache.org> on 2019/01/16 13:37:00 UTC

[jira] [Resolved] (SLING-8218) Optimise the list iteration step conditions generated by the HTL compiler

     [ https://issues.apache.org/jira/browse/SLING-8218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Radu Cotescu resolved SLING-8218.
---------------------------------
    Resolution: Fixed

Fixed in [commit 43c3b4c|https://github.com/apache/sling-org-apache-sling-scripting-sightly-compiler/commit/43c3b4c].

> Optimise the list iteration step conditions generated by the HTL compiler
> -------------------------------------------------------------------------
>
>                 Key: SLING-8218
>                 URL: https://issues.apache.org/jira/browse/SLING-8218
>             Project: Sling
>          Issue Type: Improvement
>          Components: Scripting
>    Affects Versions: Scripting HTL Compiler 1.0.22-1.4.0
>            Reporter: Radu Cotescu
>            Assignee: Radu Cotescu
>            Priority: Major
>             Fix For: Scripting HTL Compiler 1.1.2-1.4.0
>
>
> Starting with SLING-7682, the HTL compiler implements support for iteration control in {{data-sly-list}} and {{data-sly-repeat}}. However, the generated iteration control conditions always perform computations. For simple cases (e.g. {{begin}} and {{step}} are undefined), the step control condition should not be calculated and rather defined as a constant.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)