<?xml version="1.0" encoding="UTF-8"?>
<wiki>
  <body>&lt;h3&gt;&lt;code&gt;:lax&lt;/code&gt; functionality&lt;/h3&gt;
&lt;p&gt;The current &lt;code&gt;:lax&lt;/code&gt; functionality is too lax and will apply lax rules to all sub-elements being expanded. For example, if &lt;code&gt;$[oni:lax]&lt;/code&gt; is being expanded, and &lt;code&gt;oni&lt;/code&gt; is defined to be &lt;code&gt;blah $[foo]&lt;/code&gt;, then currently &lt;code&gt;foo&lt;/code&gt; does not need to be defined and will have a &amp;#8220;lax&amp;#8221; expansion performed even though it isn&amp;#8217;t explicitly labeled with a &lt;code&gt;:lax&lt;/code&gt; suffix. This should be fixed so that &lt;code&gt;:lax&lt;/code&gt; suffixes only apply to the specific variable labeled with such suffix, rather than having it apply recursively to all sub-expansions.&lt;/p&gt;
&lt;h3&gt;substring support&lt;/h3&gt;
&lt;p&gt;It would be good to add Python-style substring support, so recipes can do things like:&lt;/p&gt;
&lt;pre&gt;
[when target/subarch:0:1 is ~]
&lt;/pre&gt;</body>
  <created-at type="datetime">2009-11-24T14:39:45-08:00</created-at>
  <id type="integer">81145</id>
  <permalink>todo</permalink>
  <repository-id type="integer">56079</repository-id>
  <title>TODO</title>
  <updated-at type="datetime">2008-11-14T13:21:36-08:00</updated-at>
  <user-id type="integer">24220</user-id>
</wiki>
