Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add explicit implications #2247

Closed
wants to merge 1 commit into from

Commits on Mar 6, 2018

  1. Add explicit implications

    WORK IN PROGRESS
    
    This is a start to add explicit implications to the GAP library that can
    substitute the undocumented "hidden implications" which GAP uses so far for
    the computation of filter ranks and when checking if installed methods
    correspond to appropriate declarations.
    
    Here, we only add implications which are explicitly mentioned in the
    documentation.
    
    It can be debugged (see branch fl_nohiddenamps) that the changes here have
    almost no impact on the relative ranks of methods. Using the -N switch
    from the mentioned branch one can call gap -A -N without any messages from
    InstallMethod. But there is still some work to do because many filters have
    a much lower rank without hidden implications and a few rank changes of
    methods may need to be fixed.
    frankluebeck committed Mar 6, 2018
    Configuration menu
    Copy the full SHA
    3b8b7f5 View commit details
    Browse the repository at this point in the history