With the recent surge of golf posts, i was interested in the tricks that would come up. So i decided to copy/paste the solutions to a few different golfs into a file and set up a run or two. The first time i tried this, i was disturbed that nothing happened. After further searching i found that some of the algorithms provided in golf are so slow that they can cause machine-grinding halting for any large problem space.

My general inquiry then is: Would people be interested in a golf problem that asked for a reduction of time to solve the problem? There would be no need for a formal proof of shortness, just a listing of the benchmark or some such. i've seen merlyn and others stating sometimes one solution is better than another because it uses fewer instructions. This type of golf would be the extreme of that type of thinking, and best solutions would usually not include recursion and extraneous loops.

Methinks it's an interesting idea and worth consideration since often it's more worthwhile to optimize code than it is to shrink it's size. As a tag for the posts' title i thought of maybe [frisbee golf], but that's subject to change...

Your thoughts?
jynx

In reply to Another golf style? by jynx

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.