How to Install and Uninstall ghc-async.x86_64 Package on Fedora 34

Last updated: June 29,2024

1. Install "ghc-async.x86_64" package

Please follow the guidelines below to install ghc-async.x86_64 on Fedora 34


    
        
            $
        

        
            
                sudo dnf update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf install
            
                        
                ghc-async.x86_64
            
                    
    
    Copied

2. Uninstall "ghc-async.x86_64" package

Please follow the guidance below to uninstall ghc-async.x86_64 on Fedora 34:


    
        
            $
        

        
            
                sudo dnf remove
            
                        
                ghc-async.x86_64
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf autoremove
            
                    
    
    Copied

3. Information about the ghc-async.x86_64 package on Fedora 34

Last metadata expiration check: 2:54:27 ago on Tue Sep 6 08:10:37 2022.
Available Packages
Name : ghc-async
Version : 2.2.2
Release : 5.fc34
Architecture : x86_64
Size : 36 k
Source : ghc-async-2.2.2-5.fc34.src.rpm
Repository : fedora
Summary : Run IO operations asynchronously and wait for their results
URL : https://hackage.haskell.org/package/async
License : BSD
Description : This package provides a higher-level interface over threads, in which an
: 'Async a' is a concurrent thread that will eventually deliver a value of
: type 'a'. The package provides ways to create "Async" computations,
: wait for their results, and cancel them.
:
: Using 'Async' is safer than using threads in two ways:
:
: * When waiting for a thread to return a result, if the thread dies with an
: exception then the caller must either re-throw the exception ('wait') or handle
: it ('waitCatch'); the exception cannot be ignored.
:
: * The API makes it possible to build a tree of threads that are automatically
: killed when their parent dies (see 'withAsync').