Project

General

Profile

Design #1162

Check semantics of NoSmallFactorSeq

Added by John Abbott about 6 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Improving
Target version:
Start date:
26 Feb 2018
Due date:
% Done:

100%

Estimated time:
5.55 h
Spent time:

Description

I have just added the new class NoSmallFactorSeq but it is awkward to use.

Reconsider its public interface.

History

#1 Updated by John Abbott about 6 years ago

  • Status changed from New to Resolved
  • Assignee set to John Abbott
  • % Done changed from 0 to 60

I have introduced a new class FastMostlyPrimeSeq which produces an increasing sequence of positive integers which contains all the primes, and just a few composites. op++ is reasonably fast; much faster than for PrimeSeq.

This uses internally NoSmallFactorSeq.

#2 Updated by John Abbott about 6 years ago

  • % Done changed from 60 to 70

Currently the choice of biggest prime which is "filtered" is somewhat arbitrary.
Is it worth doing anything more refined?

#3 Updated by John Abbott almost 6 years ago

  • Status changed from Resolved to Feedback
  • % Done changed from 70 to 90

I have no ideas for improving this currently. So have moved to "feedback".

#4 Updated by John Abbott over 5 years ago

  • Status changed from Feedback to Closed
  • % Done changed from 90 to 100
  • Estimated time set to 5.55 h

Also available in: Atom PDF