Village Pump/Approximate fit solutions: Difference between revisions

In some instances, it may not be possible for a language to provide an exact match solution to the task, due to limitations of the language or its utilized subcomponents. It might be a good idea to have a "limited solution" marker would be a good idea. (Similar to the "incorrect solution" tag), that reads something like 'The solution provided does not meet the exact specifications of the task, due to limitations of the language or its subcomponents. The author has tried to provide an "approximate fit" or "best fit" solution based on those limitations'. I know there are tasks on the wiki, where the solutions is a close approximation, rather than an exact fit. This might be quite useful. This would give better scope for making comparisons of languages, because it would be possible to see the limitations of the language and it tools for a particular task, (rather than the implementation being simply omitted, giving us nothing to use for evaluation of the language at all). [[User:Markhobley|Markhobley]] 09:55, 24 July 2011 (UTC)

 

We could just have a policy that allows approximations, if an exact fit is not available, providing that the solution states the limitations and any differences in behaviour from the task requirements. [[User:Markhobley|Markhobley]] 16:49, 24 July 2011 (UTC)

:Hi Mark, we have such a policy. It is explained above. It may rely on discussion in the talk pages but has worked in the past, and should work in the future. How about listening to the emerging [[wp:Consensus decision-making|consensus]]? --[[User:Paddy3118|Paddy3118]] 19:11, 26 July 2011 (UTC)